Note… for fix to take effect, there is a bit of a chicken meets egg situation. Old code is still loaded when you run the upgrade.
You may need a ./launcher rebuild for the first time, and subsequent times the web upgrader will be fine.
No easy way around this. @cvx its a tricky problem… technically we should have it so DockerManager::Upgrader.new(user_id, repo, repo_version).upgrade shells out and runs new upgrader code when it upgrades … but its a can of snakes.
Fast workaround
- Start upgrading docker manager
- Cancel when it gets stuck
./launcher restart appfrom the shell- Upgrade from web will work.
Easy workaround
./launcher rebuild app
Everything is fine after this.
EDIT
Closing this preemptively cause I want this to be the last post on this topic. Which will make it easy for people to find the workarounds. Flag to open if still an issue after a rebuild.