im not sure but currently is working …, maybe i do something wrong , bad idea deploying with half watt of brain power looks like i need a sleep, tomorrow i will check wether or not this still an issue
Off hand those logs look like what you’d expect to see when deploying an update to an app with stopped machines. Deploys don’t automatically start machines, so for a stopped machine the “configuring firecracker” is generally the last message logged after the updates pushed. If they are stopped, starting them (either from flyctl or with autostart) should bring them up with the new image.
true, actually after checking it today this is my mistake i have 3 different fly config
fly-prod.toml
fly.toml
fly-dev.toml
and i choose wrong config to run the deploy and logs
i was waiting like 30 minutes my app is not updating and the only logs that shown is that i was confused with my 5 watt of brain power