Update stopped app without having to manually start it first

[LarsR]

The reason why has been discussed in this topic

Why must apps be running to be updated?

I don’t understand why for an app to be updated, it must be running, this is particularly curious, as for the update it’s stopped, then updated, and then redeployed. Why can’t the stop and redeploy steps be skipped and an app at rest be updated?

and the reason was stated in this post

Why must apps be running to be updated?

My memory from the last time I asked a dev about this is that it has to do with a concern about data integrity. As far as I understand it, their concern is that it’s less disruptive to stop and restart a running app (and then let it stay running after) than to allow docker to start a stopped app as part of the upgrade process and then immediately stop it again. The idea being that starting and then quickly stopping the app would increase the risk that data might be in an unsafe state as part of …