Initial deploy failing with '500 Internal Server Error'

My initial deploy of a new Rails 7 app keeps failing with the below error. I am new to Fly, but from what I’m reading this seems to be unexpected. Could this be an issue on the Fly side?

fly deploy
==> Verifying app config
Validating /Users/austinwasson/fgai/tailor/fly.toml
Platform: machines
✓ Configuration is valid
--> Verified app config
==> Building image
Remote builder fly-builder-dry-paper-3721 ready
==> Building image with Docker
--> docker host: 20.10.12 linux x86_64
[+] Building 1.5s (25/25) FINISHED
 => [internal] load build definition from Dockerfile                                                0.7s
 => => transferring dockerfile: 32B                                                                 0.7s
 => [internal] load .dockerignore                                                                   0.7s
 => => transferring context: 35B                                                                    0.7s
 => resolve image config for                                          0.3s
 => CACHED docker-image://  0.0s
 => [internal] load build definition from Dockerfile                                                0.0s
 => [internal] load metadata for                                  0.2s
 => [internal] load .dockerignore                                                                   0.0s
 => [internal] load build context                                                                   0.2s
 => => transferring context: 17.75kB                                                                0.2s
 => [base 1/3] FROM  0.0s
 => CACHED [base 2/3] WORKDIR /rails                                                                0.0s
 => CACHED [base 3/3] RUN gem update --system --no-document &&     gem install -N bundler           0.0s
 => CACHED [stage-2 1/4] RUN apt-get update -qq &&     apt-get install --no-install-recommends -y   0.0s
 => CACHED [build 1/9] RUN apt-get update -qq &&     apt-get install --no-install-recommends -y bu  0.0s
 => CACHED [build 2/9] RUN curl -sL | t  0.0s
 => CACHED [build 3/9] COPY --link Gemfile Gemfile.lock ./                                          0.0s
 => CACHED [build 4/9] RUN bundle install &&     bundle exec bootsnap precompile --gemfile &&       0.0s
 => CACHED [build 5/9] COPY --link package.json package-lock.json ./                                0.0s
 => CACHED [build 6/9] RUN npm install                                                              0.0s
 => CACHED [build 7/9] COPY --link . .                                                              0.0s
 => CACHED [build 8/9] RUN bundle exec bootsnap precompile app/ lib/                                0.0s
 => CACHED [build 9/9] RUN SECRET_KEY_BASE_DUMMY=1 ./bin/rails assets:precompile                    0.0s
 => CACHED [stage-2 2/4] COPY --from=build /usr/local/bundle /usr/local/bundle                      0.0s
 => CACHED [stage-2 3/4] COPY --from=build /rails /rails                                            0.0s
 => CACHED [stage-2 4/4] RUN useradd rails --create-home --shell /bin/bash &&     chown -R rails:r  0.0s
 => exporting to image                                                                              0.0s
 => => exporting layers                                                                             0.0s
 => => writing image sha256:085767ceb7c2a74c96e63dec0b99caa64bcb71144edec3f82f87fe2897d571a2        0.0s
 => => naming to                       0.0s
--> Building image done
==> Pushing image to fly
The push refers to repository []
de9de657d7ed: Retrying in 1 second
dc27f45cf43e: Retrying in 1 second
1d6543cbcb7b: Retrying in 1 second
2a9169c55307: Retrying in 1 second
5c251c3afa6d: Retrying in 1 second
f286ae347267: Waiting
1114f0f413de: Waiting
1c9545e83e70: Waiting
a7db04affd22: Waiting
79b889099ebe: Waiting
92770f546e06: Waiting
Error: failed to fetch an image or build from source: error rendering push status stream: received unexpected HTTP status: 500 Internal Server Error```

Sorry for the inconvenience. We had a registry incident in that Friday.

It has been resolved. Let me know if you still have the issue.

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