I have tried recommitting the code. I have redeployed and destroyed machines.
the machine itself gets stuck in the following state:
ID NAME STATE REGION IMAGE IP ADDRESS VOLUME CREATED LAST UPDATED APP PLATFORM PROCESS GROUP SIZE
5683923f15398e floral-fog-8022 created sin nvwweb:deployment-01HE5J7ETMHM32Q810RQC37WSD fdaa:0:6d28:a7b:a754:e736:d85c:2 2023-11-01T13:47:42Z 2023-11-01T13:47:42Z v2 fly_app_release_command shared-cpu-2x:512MB
Any pointers would be helpful…
I can not get the machine to “started” state. Maybe there is something wrong with the app/bin/migrate but a little vague
increasing the --wait-timeout to 1800 seconds might help work around this - it will take a while but at least the deployment shouldn’t break
If you want something faster: Notice that what’s failing is the release_command, and this works by creating an ephemeral machine in your primary region, running the release command, and then deleting the machine. So another thing you can try is forcing a different primary region for the deployment so the release_command machine is created in a region that’s not affected by image pull issues:
PRIMARY_REGION=hkg fly deploy
and of course, we’re looking at this random slowness pulling images in that particular region so these workarounds are not needed anymore.
Thank you. THe longer timeout allowed me to deploy successfully.
I get the following error despite the app still working.
he app is not listening on the expected address and will not be reachable by fly-proxy.35b105789 [app] update finished: success
and it suggests to
You can fix this by configuring your app to listen on the following addresses: