Skip to content

Classify OrbStack's offline pull as a lost download - #7

Merged
MasterYoav merged 1 commit into
masterfrom
orbstack-offline
Sep 18, 2026
Merged

MasterYoav merged 1 commit into
masterfrom
orbstack-offline

Conversation

@MasterYoav

Copy link
Copy Markdown
Owner

Checked the failure classifier against real docker output on this Mac (OrbStack 29.4) instead of assumed phrasing:

Real message Classified Right?
manifest unknown imageUnavailable yes
…/manifests/1": denied imageUnavailable yes
Bind for 127.0.0.1:49399 failed: port is already allocated portInUse yes
Get "https://…/v2/": Bad Gateway (registry unreachable) other no

OrbStack's daemon goes through a proxy, so an unreachable registry reaches us as the proxy's answer rather than Docker Desktop's no such host. It fell through to "The engine couldn't start" — on a first run with the network down, on the runtime a developer's Mac most likely already has. Now it reads as an interrupted download, whose sentence says to check the connection and that finished layers are kept.

Test first, using the exact line OrbStack printed. Full Swift suite green.

🤖 Generated with Claude Code

Measured against OrbStack 29.4: an unreachable registry comes back as the
proxy's answer, which fell through to "The engine couldn't start" on a
first run with the network down.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@MasterYoav
MasterYoav merged commit 00fd9e0 into master Sep 18, 2026
3 checks passed
@MasterYoav
MasterYoav deleted the orbstack-offline branch September 18, 2026 07:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant