500 internal server error in fly.io release/deploy of pre-built docker image

Hi since some days ago I get 500 status codes in github CI when making a new release / deploy of existing apps. Nothing changed on my end and the docker image for sure works and can be pulled. Seems an internal error in fly. What can I do? Or is this a known issue. Example CI output log:

```
cd <fly.toml path>

flyctl deploy --verbose --remote-only

shell: /usr/bin/bash -e {0}

env:

CARGO_TERM_COLOR: always

RUST_TOOLCHAIN: stable

RUST_TOOLCHAIN_NIGHTLY: nightly

RUST_TOOLCHAIN_MSRV: 1.91.0

RUST_TOOLCHAIN_BETA: beta

FLY_API_TOKEN: ***

==> Verifying app config

- → Verified app config

Validating /home/runner/work//fly.toml

✓ Configuration is valid

==> Building image

Searching for image ‘/:latest’ remotely…

Watch your deployment at https://fly.io/apps/monitoring

Error: failed to create release (status 500):

We're sorry, but something went wrong (500) body { background-color: #EFEFEF; color: #2E2F30; text-align: center; font-family: arial, sans-serif; margin: 0; } div.dialog { width: 95%; max-width: 33em; margin: 4em auto 0; } div.dialog > div { border: 1px solid #CCC; border-right-color: #999; border-left-color: #999; border-bottom-color: #BBB; border-top: #B00100 solid 4px; border-top-left-radius: 9px; border-top-right-radius: 9px; background-color: white; padding: 7px 12% 0; box-shadow: 0 3px 8px rgba(50, 50, 50, 0.17); } h1 { font-size: 100%; color: #730E15; line-height: 1.5em; } div.dialog > p { margin: 0 0 1em; padding: 1em; background-color: #F7F7F7; border: 1px solid #CCC; border-right-color: #999; border-left-color: #999; border-bottom-color: #999; border-bottom-left-radius: 4px; border-bottom-right-radius: 4px; border-top-color: #DADADA; color: #666; box-shadow: 0 3px 8px rgba(50, 50, 50, 0.17); }

We're sorry, but something went wrong.

If you are the application owner check the logs for more information.

Error: Process completed with exit code 1.
```

Kind regards
Glen

FWIW a restart of the CI jobs usually makes it work, but not always. And prior to a couple of days ago I never saw this issue before… It’s not a blocker but ideally we get it resolved together…

Hi… This looks very similar to the following ongoing thread:

https://community.fly.io/t/random-and-intermittent-deployment-error-500-fly-rails-infra-bug/26566

It would probably help to provide the additional information requested there, if you can, :thinking: