Cannot deploy due to Docker error

21

same here, region Singapore

22

Same here, LAX

23

same here SJC

24

same here LAX

25

Ok, I’m not the only one :slightly_smiling_face:

26

Hi folks, we’re investigating this issue now and will post updates to: Fly.io Status - Deployments fail to load metadata from docker.io

1 Like
27

Same issue here failed to create LLB definition: docker.io/hexpm/elixir:1.15.6-erlang-26.1.1-debian-bullseye-20210902-slim: not found. Any update?

28

It’s happening again…
#3 [internal] load metadata for docker.io/library/node:16-bullseye-slim
#3 ERROR: unexpected status code [manifests 16-bullseye-slim]: 503 Service Unavailable

29

Same here for Golang:

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 latest]: 503 Service Unavailable

30

I got same issue:

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

1 Like
31

I’m experiencing the same issue:

Error: failed to fetch an image or build from source: error building: failed to solve: failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: unexpected status code [manifests 1]: 503 Service Unavailable

32

same for me

33

I am also currently experiencing this issue.

FWIW, our builder instance machine is located in the IAD region, in case there is a region-specific connectivity issue ongoing between Fly.io and Docker Hub.

34

Experiencing this too, in the UK region.

35

Same here:

WARN Failed to start remote builder heartbeat: server returned a non-200 status code: 504

36

don’t think it’s region specific. LAX here.

37

facing same issue

38

went to bed, worked for me when I got up.