ERROR [internal] load metadata for docker.io/library/python:3.11-buster 503 Service Unavailable

1

Have been receiving this error for a few hours when trying to fly deploy

[+] Building 84.7s (3/3) FINISHED
=> [internal] load build definition from Dockerfile.web 0.1s
=> => transferring dockerfile: 157B 0.1s
=> [internal] load .dockerignore 0.1s
=> => transferring context: 35B 0.1s
=> ERROR [internal] load metadata for Docker 84.6s

[internal] load metadata for Docker

Error: failed to fetch an image or build from source: error building: failed to solve: failed to solve with frontend dockerfile.v0: failed to create LLB definition: unexpected status code [manifests 3.11-buster]: 503 Service Unavailable

3 Likes
2

am seeing the same issue here.

1 Like
3

fly deploy --local-only has unblocked me for now

2 Likes
4

Image built fine, took awhile on my local machine.

But now I’m seeing this error when waiting for it to deploy :unamused:

-------
 ✖ Failed: error waiting for release_command machine 3287310f302d85 to start: timeout reached waiting for machine to started faile…
-------
Error: release command failed - aborting deployment. error waiting for release_command machine 3287310f302d85 to start: timeout reached waiting for machine to started failed to wait for VM 3287310f302d85 in started state: Get "https://api.machines.dev/v1/apps/****&state=started&timeout=60": net/http: request canceled
You can increase the timeout with the --wait-timeout flag

Destroyed that machine, and now currently stuck:

2023-10-14T04:37:30.429 runner[9080e453fe1187] sjc [info] Pulling container image registry.fly.io/*******
1 Like
5

same issue. just necro’d an old post that had a similiar issue, something about mirror proxies.

1 Like
6

same problem

2 Likes
7

Neither worked for me --local-only nor --remote-only resulted in the following error

Error: failed to fetch an image or build from source: error building: failed to solve: failed to solve with frontend dockerfile.v0: failed to create LLB definition: unexpected status code [manifests 3.11-alpine]: 503 Service Unavailable

1 Like
8

for me too :metal:t2:

9

Ye im getting all kinds of docker related issues. Looks like Fly’s docker repo is having issues.

10

Same issue:

#3 [internal] load metadata for docker.io/library/node:18-bullseye-slim
#3 ERROR: unexpected status code [manifests 18-bullseye-slim]: 503 Service Unavailable
------
 > [internal] load metadata for docker.io/library/node:18-bullseye-slim:
------
Error: failed to fetch an image or build from source: error building: failed to solve: failed to solve with frontend dockerfile.v0: failed to create LLB definition: unexpected status code [manifests 18-bullseye-slim]: 503 Service Unavailable
Error: Process completed with exit code 1.

--local-only works for me

Had to change the CI deploy in GH Action to:

flyctl deploy --remote-only --build-arg COMMIT_SHA=${{ github.sha }} --app ${{ steps.app_name.outputs.value }} || flyctl deploy --local-only --build-arg COMMIT_SHA=${{ github.sha }} --app ${{ steps.app_name.outputs.value }}
11

Thanks for the reports, folks. We’re looking into a potential cause with our registry mirror. Follow this issue at Fly.io Status - "fly deploy" experiencing issues with deploys potentially failing on our status page. https://status.flyio.net/

2 Likes
12

This should be mitigated now.

1 Like
13

I’m still having trouble with deploying my phoenix app w/ postgres.
I used to get the same 503 error, but now it’s constantly timing out.

 ✖ Failed: error waiting for release_command machine e2865996a11686 to start: timeout reached waiting for machine to started failed to wait for VM e2865996a11686 in started state.
-------
Error: release command failed - aborting deployment. error waiting for release_command machine e2865996a11686 to start: timeout reached waiting for machine to started failed to wait for VM e2865996a11686 in started state: Get "https://api.machines.dev/v1/apps/ekmi/machines/e2865996a11686/wait?instance_id=01HCTWP7CEKY6CC26RYDBTXGPY&state=started&timeout=60": net/http: request canceled
You can increase the timeout with the --wait-timeout flag

My deployment server is Hong Kong.

any ideas?

14

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.