What it says in the title. Watching the logs shows no machine is spawned to even be unhealthy
new error output:
Recent Events TIMESTAMP TYPE MESSAGE 2023-02-25T23:51:28Z Received Task received by client 2023-02-25T23:51:28Z Task Setup Building Task Directory 2023-02-25T23:51:31Z Driver Failure rpc error: code = Unknown desc = could not fulfill runtime memory request 2023-02-25T23:51:31Z Not Restarting Error was unrecoverable 2023-02-25T23:51:31Z Alloc Unhealthy Unhealthy because of failed task
Seems to only be an issue with nomad apps, i destroyed the app and recreated it with machines and all is working
Also happening with my nomad apps.
Managed to deploy by, instead of using a ‘bluegreen’ strategy, choosing ‘immediate’:
fly deploy --remote-only --strategy immediate --config fly.toml
I am blocked on this since yesterday, not able to deploy my app for the same reason.
--strategy immediate fixed it for me too, thank you.
--strategy immediate fixed it for me as well.
The issue is easily reproducible with Remix Run app:
flyctand authenticate it
- Create a new Remix Run app
cdinto the app folder and initialize Fly.io
flyctl launch: choose all defaults and agree to deploy
- Change literally any symbol in, say,
app/routes/index.jsxof the app, try
flyctl deployand see failure
- Revert the change, try
flyctl deployand see success
I guess there is probably an even easier way to reproduce, it doesn’t seem to be tied to Remix, it’s just I’m sure this one is stable.
I’m also unable to deploy since yesterday (last succesful deploy 15h28m ago), but I get no errors. It just fails on release with:
--> release v20 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. Error release command failed, deployment aborted
Adding --strategy immediate doesn’t change anything so it might be another cause. Any suggestions?
Platform = nomad
Seeing the same on my postgres app, I can’t use the
immediate strategy there, can’t restart it, can’t scale it… Truly disappointed with all the problems past weeks.
Waiting for the fix as I am blocked
Similar issue here in
--strategy immediate works, but moving region also seems to work.
==> Creating release --> release v79 created --> You can detach the terminal anytime without stopping the deployment ==> Release command detected: php artisan migrate --force --> This release will not be available until the release command succeeds. Error release command failed, deployment aborted
Changing region (and creating a new db) worked for me.
Which region is working? I tried
sin and it didn’t work.
ams is NOT working, but lhr and cdg are. lhr seems a bit slow.
Hi all, we’re working to provision more capacity in
ams and are also adjusting resource allocation. Feel free to follow Fly.io Status - Capacity Issues in AMS region for updates.