warpdotdev/warp · error

Failed to fetch images: {err}

Error message

Failed to fetch images: {err}

What it means

Reported by report_fatal_error inside prompt_for_docker_image when the async send_graphql_request for ListWarpDevImages returns Err during environment creation without --docker-image. The transport-level error text is appended ('Failed to fetch images: {err}'). This is the create-path counterpart of error 102.

Source

Thrown at app/src/ai/agent_sdk/environment.rs:417

                                }
                                return;
                            }
                        }
                    } else {
                        selected_image
                    };

                    continuation(final_image, ctx);
                }
                ListWarpDevImagesResult::UserFacingError(_) | ListWarpDevImagesResult::Unknown => {
                    super::report_fatal_error(
                        anyhow::anyhow!("Failed to fetch list of base images"),
                        ctx,
                    );
                }
            },
            Err(err) => {
                super::report_fatal_error(anyhow::anyhow!("Failed to fetch images: {err}"), ctx);
            }
        });
    }

    #[allow(clippy::too_many_arguments)]
    fn create(
        &mut self,
        name: String,
        description: Option<String>,
        docker_image: Option<String>,
        github_repos: Vec<GithubRepo>,
        setup_commands: Vec<String>,
        scope: warp_cli::scope::ObjectScope,
        ctx: &mut ModelContext<Self>,
    ) {
        if let Some(image) = docker_image {
            Self::create_with_image(
                name,

View on GitHub (pinned to e72fd7aacb)

Solutions

1. Restore connectivity to the server endpoint and retry
2. Supply --docker-image to bypass the remote image list completely
3. For local dev, start warp-server and confirm SERVER_ROOT_URL/WS_SERVER_URL (e.g. port 8082) match
4. Check proxies/firewalls if in a restricted environment

// Connectivity preflight before interactive create:
// curl -fsS --max-time 5 "$SERVER_ROOT_URL" -o /dev/null || echo "unreachable — pass --docker-image"

Err(err) => {
    // transport failure fetching images: classify and either retry or bypass the prompt
    // by requiring an explicit --docker-image
}

When it happens

Trigger: Running `warp environment create` (no --docker-image) with the server unreachable, DNS failure, TLS interception, HTTP error status, or a WebSocket/GraphQL protocol failure on the request.

Common situations: Offline or proxied networks; local warp-server not running or wrong SERVER_ROOT_URL port; transient outages; firewall blocking the server host.

Related errors

• Failed to fetch images: {}
• Timed out refreshing team metadata
• Failed to fetch images
• Timed out waiting for Warp Drive to sync
• Failed to fetch list of base images

AI-assisted analysis of warpdotdev/warp@e72fd7aacb (2026-08-16). Data as JSON: /api/errors/b281ddca520f4699. Report an issue: GitHub.