Deployment freezes forever

Questions / Help Build debugging
1

deployments have stopped working for me
they get stuck in here no errors just the spinning globe

not sure if it is relevant but at some point a build error because i removed a js file from the app
but i believe since i haven’t been able to deploy

→ Pushing image done
image: registry.fly.io/app_name:deployment-id
image size: 1.1 GB
==> Creating release
→ release v18 created

→ You can detach the terminal anytime without stopping the deployment
==> Release command detected: bin/rails fly:release

→ This release will not be available until the release command succeeds.

2

I am experiencing the same issue since yesterday :sleepy: with the flyctl GitHub Action.

3

Also experiencing this issue. Here is some of the output just in case it’s helpful.

==> Pushing image to fly
The push refers to repository [registry.fly.io/frosty-the-dm-bear]
7da29f12da22: Layer already exists 
ee4c8f681c92: Layer already exists 
cd3a0ba91a0e: Layer already exists 
cb0a20f87b95: Layer already exists 
6ef098cc49bc: Layer already exists 
fe7b1e9bf792: Layer already exists 
deployment-01GREHKAZD4ZRTF1JDJ1PSF32N: digest: sha256:6c88cb223a0fee73be3970bc3dda085d97da76c90fe92592f5e7b2f314cf6f55 size: 1576
--> Pushing image done
image: registry.fly.io/xxxxxxxxxxxx:deployment-01GREHKAZD4ZRTF1JDJ1PSF32N
image size: 137 MB
==> Creating release
--> release v52 created

--> You can detach the terminal anytime without stopping the deployment
==> Release command detected: /app/bin/migrate

--> This release will not be available until the release command succeeds.
Running release task (pending)...

This is an elixir/phx app, not rails. Not sure if that is meaningful.

4

Feels related:

5

Same issue here in FRA.

6

Experiencing same issue here.

7

If you have a Rails application with a single server in a single region, I recommend removing or commenting out:

# [deploy]
#   release_command = "bin/rails db:prepare"

Then deleting `lib/rails/fly.rake’ and then running:

bundle add dockerfile-rails --optimistic --group development
bin/rails generate dockerfile

… and accepting the changes.

That will bring you up to date with the latest changes to flyctl launch. You are also encouraged to read Dockerfiles and fly.toml · Fly Docs to see if there are any suggestions that you might want to take advantage of.

If you have a heavily customized Dockerfile or have another reason why you don’t want to accept the Dockerfile changes, create a two line script that runs your current release command followed by your current CMD from the Dockerfile, and then change the CMD to run your script.

For non-Rails applications with a single server in a single region, the same recommendations apply other than not having the benefit of a script.

1 Like
8

Removing the release task from my elixir/phoenix fixed my deployment issue. Thanks.

9

Same issue here. Deploys don’t work and get stuck at “Running Release Task”.
Doesn’t matter whether kicked off manually with flyctl deploy or Github actions.

FRA region, Phoenix project.

10

Thanks! Just commenting out this line in fly.toml fixed it for me:

# [deploy]
#  release_command = "bin/rails fly:release"
11

That worked here as well - there’s also finally a message online:

image
image1780×468 41.7 KB

12

hey sam

while removing the deploy command fixed the deployment issue
running

bundle add dockerfile-rails --optimistic --group development
bin/rails generate dockerfile

somehow broke access to the volume and it is giving me OOM errors when asking for screenshots

13

Should not have affected volumes, but Rails’s new conventions do differ from fly’s previous ones in that the app is at /rails instead of /app, and the port is now 3000 rather than 8080. Were you mounting the volume into the /app directory?

Rails template doesn’t include fullstaq, jemalloc, or a swapfile. You can add them with simple commands: Dockerfiles and fly.toml · Fly Docs

14

thanks! i will look into it