# Fly deploy failing at resolving Docker image config **URL:** \ **Category:** Questions / Help\ **Tags:** rails, login-only\ **Created:** [October 14, 2023, 5:21am UTC](https://community.fly.io/t/fly-deploy-failing-at-resolving-docker-image-config/15893 "2023-10-14T05:21:16Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![sastreen](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@sastreen](https://community.fly.io/u/sastreen)\ **Post date:** [October 14, 2023, 5:21am UTC](https://community.fly.io/t/fly-deploy-failing-at-resolving-docker-image-config/15893/1 "2023-10-14T05:21:16Z")
Hey all - I’m getting this error: ```auto => ERROR resolve image config for docker.io/docker/dockerfile:1 85.0s 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 ``` That sounds a lot like the Docker registry is down, though the [status page](https://www.dockerstatus.com) says it isn’t. What other problems could it be related to? Commits that previously deployed without problem are failing. Alternatively, is there another registry I could use instead for: ```auto ARG RUBY_VERSION=3.2.2 FROM ruby:$RUBY_VERSION-slim as base ``` ? ---
**Author:** ![al0xd](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/al0xd/32/14383_2.png) [@al0xd](https://community.fly.io/u/al0xd)\ **Post date:** [October 14, 2023, 9:13am UTC](https://community.fly.io/t/fly-deploy-failing-at-resolving-docker-image-config/15893/2 "2023-10-14T09:13:06Z")
I also got the same error, couldn’t deploy the project for almost 8 hours!!! ---
**Author:** ![nclevenger](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/nclevenger/32/15712_2.png) [@nclevenger](https://community.fly.io/u/nclevenger)\ **Post date:** [October 14, 2023, 9:19am UTC](https://community.fly.io/t/fly-deploy-failing-at-resolving-docker-image-config/15893/3 "2023-10-14T09:19:02Z")
us too - we are unable to deploy any of our [fly.io](http://fly.io) projects … we’re using the `node:20-alpine` image our error messages is: ```auto 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 20-alpine]: 503 Service Unavailable ``` ---
**Author:** ![unathi](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/unathi/32/15714_2.png) [@unathi](https://community.fly.io/u/unathi)\ **Post date:** [October 14, 2023, 9:26am UTC](https://community.fly.io/t/fly-deploy-failing-at-resolving-docker-image-config/15893/4 "2023-10-14T09:26:19Z")
I get the same error as those above. Found I could get it to work by running the docker build locally: ```auto flyctl deploy --local-only ``` ---
**Author:** ![lifeofguenter](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/lifeofguenter/32/15679_2.png) [@lifeofguenter](https://community.fly.io/u/lifeofguenter)\ **Post date:** [October 14, 2023, 9:32am UTC](https://community.fly.io/t/fly-deploy-failing-at-resolving-docker-image-config/15893/5 "2023-10-14T09:32:16Z")
Thanks @unathi - this is the way, was searching for this option. ---
**Author:** ![al0xd](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/al0xd/32/14383_2.png) [@al0xd](https://community.fly.io/u/al0xd)\ **Post date:** [October 14, 2023, 9:52am UTC](https://community.fly.io/t/fly-deploy-failing-at-resolving-docker-image-config/15893/6 "2023-10-14T09:52:51Z")
Thank you!! I’m trying it and it seems to work ---
**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:03pm UTC](https://community.fly.io/t/fly-deploy-failing-at-resolving-docker-image-config/15893/7 "2023-10-14T13:03:06Z")
👋 > [@ERROR \[internal\] load metadata for docker.io/library/python:3.11-buster 503 Service Unavailable](https://community.fly.io/t/error-internal-load-metadata-for-docker-io-library-python-3-11-buster-503-service-unavailable/15891/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](https://status.flyio.net/incidents/f9ytx5rbzv46) on our status page. [https://status.flyio.net/](https://status.flyio.net/) ---
**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:27pm UTC](https://community.fly.io/t/fly-deploy-failing-at-resolving-docker-image-config/15893/8 "2023-10-14T13:27:47Z")
> [@Failed to start remote builder heartbeat: server returned a non-200 status code: 500](https://community.fly.io/t/failed-to-start-remote-builder-heartbeat-server-returned-a-non-200-status-code-500/15860/45): > > This incident status has been updated; deployments should be working now. ---
**Author:** ![system](https://global.discourse-cdn.com/fly1/original/3X/6/e/6e8955d00cb218e186ebbe3a6ab06fefdce15290.svg) [@system](https://community.fly.io/u/system)\ **Post date:** [October 21, 2023, 1:28pm UTC](https://community.fly.io/t/fly-deploy-failing-at-resolving-docker-image-config/15893/9 "2023-10-21T13:28:42Z")
Closed on October 21, 2023, 1:28pm UTC This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.