Skip to content

Improve Docker image pull error message for network connectivity failures (REMOTE-2322) - #115

Draft
seemeroland wants to merge 1 commit into
mainfrom
oz-agent/REMOTE-2322
Draft

Improve Docker image pull error message for network connectivity failures (REMOTE-2322)#115
seemeroland wants to merge 1 commit into
mainfrom
oz-agent/REMOTE-2322

Conversation

@seemeroland

Copy link
Copy Markdown
Contributor

Summary

Improves the error message emitted by oz-agent-worker when Docker image pull fails due to a network connectivity error, addressing REMOTE-2322 action item #3 (improve user-facing error messages when cloud runs fail due to network connectivity issues).

Problem

Previously, when ImagePull failed with a network error, the logged message was a generic:

failed to pull image warpdotdev/dev-ubuntu:latest: dial tcp <ip>:443: i/o timeout

This gave no context about why the connection might be failing, making it harder to diagnose allowlist gaps.

Change

Adds isDockerNetworkError() which recognizes net.OpError, url.Error, and string-based network error indicators (connection refused, dial tcp, etc.).

When a network error is detected during image pull, the error message now includes a hint:

failed to pull image warpdotdev/dev-ubuntu:latest: network connectivity error reaching Docker Hub —
this may indicate that Docker Hub has added new egress IP addresses that are not yet allowlisted
in this environment's network configuration: dial tcp <ip>:443: i/o timeout

Non-network failures (auth errors, missing images, rate limits) continue to produce the original simpler message.

Testing

  • go build ./... passes
  • go test ./internal/worker/... passes (all existing tests continue to pass)

Conversation: https://staging.warp.dev/conversation/ce430aa1-c96c-4c67-8312-e63b2d8bf3ec
Run: https://oz.staging.warp.dev/runs/019f95f3-a68d-70cf-9c37-1321a20d5b08

This PR was generated with Oz.

When oz-agent-worker fails to pull a Docker image due to a network
connectivity error (connection refused, dial timeout, no such host),
add a hint that the failure may be caused by Docker Hub adding new
egress IP addresses not yet allowlisted in the environment.

This addresses REMOTE-2322 action item #3: improve user-facing error
messages when cloud runs fail due to network connectivity issues.

Previously the error was a generic 'failed to pull image X: <low-level
network error>' which gave no context about the likely root cause.

The improved message distinguishes network errors from other pull
failures (auth errors, missing images) so operators can quickly
identify allowlist gaps vs. other issues.

Co-Authored-By: Oz <oz-agent@warp.dev>
@seemeroland seemeroland added the from-feedback-bot Linear issue delegated from Feedback Bot label Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

from-feedback-bot Linear issue delegated from Feedback Bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant