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

**URL:** <https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891>\
**Category:** General\
**Tags:** login-only\
**Created:** [October 14, 2023, 3:56am UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891 "2023-10-14T03:56:55Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![wobbleburger](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/wobbleburger/32/13777_2.png) [@wobbleburger](https://community.fly.io/u/wobbleburger)\
**Post date:** [October 14, 2023, 3:56am UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/1 "2023-10-14T03:56:56Z")

</div>

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 Hub Container Image Library | App Containerization](http://docker.io/library/python:3.11-buster) 84.6s

> [internal] load metadata for [Docker Hub Container Image Library | App Containerization](http://docker.io/library/python:3.11-buster:)

* * *

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

---

<div class="post-metadata">

**Author:** ![catgirl](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/catgirl/32/42134_2.png) [@catgirl](https://community.fly.io/u/catgirl)\
**Post date:** [October 14, 2023, 4:08am UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/2 "2023-10-14T04:08:29Z")

</div>

am seeing the same issue here.

---

<div class="post-metadata">

**Author:** ![wobbleburger](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/wobbleburger/32/13777_2.png) [@wobbleburger](https://community.fly.io/u/wobbleburger)\
**Post date:** [October 14, 2023, 4:19am UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/3 "2023-10-14T04:19:38Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![wobbleburger](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/wobbleburger/32/13777_2.png) [@wobbleburger](https://community.fly.io/u/wobbleburger)\
**Post date:** [October 14, 2023, 4:21am UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/4 "2023-10-14T04:21:17Z")

</div>

Image built fine, took awhile on my local machine.

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

```auto
-------
 ✖ 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:

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

```

---

<div class="post-metadata">

**Author:** ![JFTActual](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/jftactual/32/15704_2.png) [@JFTActual](https://community.fly.io/u/JFTActual)\
**Post date:** [October 14, 2023, 4:45am UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/5 "2023-10-14T04:45:31Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![skamba](https://avatars.discourse-cdn.com/v4/letter/s/6bbea6/32.png) [@skamba](https://community.fly.io/u/skamba)\
**Post date:** [October 14, 2023, 10:28am UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/6 "2023-10-14T10:28:55Z")

</div>

same problem

---

<div class="post-metadata">

**Author:** ![sultan](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/sultan/32/15716_2.png) [@sultan](https://community.fly.io/u/sultan)\
**Post date:** [October 14, 2023, 11:16am UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/7 "2023-10-14T11:16:12Z")

</div>

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`

---

<div class="post-metadata">

**Author:** ![RoastLukas](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/roastlukas/32/12946_2.png) [@RoastLukas](https://community.fly.io/u/RoastLukas)\
**Post date:** [October 14, 2023, 11:37am UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/8 "2023-10-14T11:37:44Z")

</div>

> [@wobbleburger](#):
>
> ```auto
> g 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:
> 
> ```auto
> 2023-10-14T04:37:30.429 runner[9080e453fe1187] sjc [info] Pulling container image registry.fly.io/ *******
> 
> ```

for me too 🤘🏻

---

<div class="post-metadata">

**Author:** ![mike-cann](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/mike-cann/32/13595_2.png) [@mike-cann](https://community.fly.io/u/mike-cann)\
**Post date:** [October 14, 2023, 11:40am UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/9 "2023-10-14T11:40:27Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![st0nefree](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/st0nefree/32/15719_2.png) [@st0nefree](https://community.fly.io/u/st0nefree)\
**Post date:** [October 14, 2023, 12:04pm UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/10 "2023-10-14T12:04:15Z")

</div>

Same issue:

```auto
#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:

```auto
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 }}

```

---

<div class="post-metadata">

**Author:** ![catflydotio](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/catflydotio/32/14559_2.png) [@catflydotio](https://community.fly.io/u/catflydotio)\
**Post date:** [October 14, 2023, 12:57pm UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/11 "2023-10-14T12:57:03Z")

</div>

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](https://status.flyio.net/incidents/f9ytx5rbzv46) on our status page. [https://status.flyio.net/](https://status.flyio.net/)

---

<div class="post-metadata">

**Author:** ![catflydotio](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/catflydotio/32/14559_2.png) [@catflydotio](https://community.fly.io/u/catflydotio)\
**Post date:** [October 14, 2023, 1:29pm UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/12 "2023-10-14T13:29:42Z")

</div>

This should be mitigated now.

---

<div class="post-metadata">

**Author:** ![wjlee](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/wjlee/32/15307_2.png) [@wjlee](https://community.fly.io/u/wjlee)\
**Post date:** [October 16, 2023, 12:22am UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/13 "2023-10-16T00:22:06Z")

</div>

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.

```auto
 ✖ 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?

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/fly1/original/3X/6/e/6e8955d00cb218e186ebbe3a6ab06fefdce15290.svg) [@system](https://community.fly.io/u/system)\
**Post date:** [October 23, 2023, 12:22am UTC](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/14 "2023-10-23T00:22:48Z")

</div>

Closed on October 23, 2023, 12:22am UTC

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