Just to add an extra voice rather than any answers…
I have a tiny 1GB DO test site with lots of plugins, so it’s not normally the quickest. However, I think it’s been taking a lot longer recently too, and mine got caught in a weirdness the other day like @MarcP and I had to reset it.
I have never timed it before, but today I set it to ‘Update All’ and made a note of when I clicked the button. So far we have a 9:30 am start, and it’s still going at 10:15. It’s currently bundling some assets. I can say with some confidence that it doesn’t normally take over 45 minutes and counting to do its thing.
Though it looks like it had some permission issues purging temp files? Not sure if that’s relevant.
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.
Start upgrading docker manager
Cancel when it gets stuck
./launcher restart app from the shell
Upgrade from web will work.
./launcher rebuild app
Everything is fine after this.
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.