Apologies if this is a dumb question as I’ve just started using Fly today. I had assumed that when I deploy new code, it would kill the old instance automatically. Instead, the old instance continues running alongside the new instance that is started up after I deploy new code. Should I just be kill…

Update: I changed my deployment strategy to rolling in the TOML file, and it now kills the first instance and then spins up the new one as I wanted. Thanks for all the help and the quick responses @ignoramous :sweat_smile:

Old instance does not shut down after deploying code

Questions / Help

ignoramous January 2, 2023, 9:13am 2

Could be a Fly control plane issue:

Topic		Replies	Views
Question on deployment lifecycle (wait before kill) Questions / Help	3	677	June 19, 2023
old VM is hanging / unable to kill old VM instance Questions / Help	7	721	October 28, 2022
VM won't shut down Questions / Help	12	631	June 1, 2022
Zombie app instance running Questions / Help	3	507	October 13, 2022
Deployment handling open connections Questions / Help postgres	3	27	October 1, 2024

Old instance does not shut down after deploying code

Related topics