Upgrading to Ubuntu 22 - Recreating containers
benborges last edited by girish
So on Friday I launched an upgrade process to move from Ubuntu 20 to Ubuntu 22.
I followed the doc here https://docs.cloudron.io/guides/upgrade-ubuntu-22/
And everything appears to be going as planned, but the recreating containers script part is running since Friday and is still not over, progress is still ongoing, I see little dot on my terminal displaying fine every few seconds but I have no idea what this script is doing, there is nothing that indicate containers are being regenerated, the box is literally doing nothing but printing dots on my terminal.
I'm worried of interrupting the process, I don't know where I am in the process.
I obviously have full backups and snapshot ready, so I can go back anytime but if I can get this done and finished, I'd rather stay on Ubuntu 22.
Any hint, is it normal that this container cgroup v2 recreation is taking.....Days & Nights ?
I had perhaps some 40 containers running, some bigger than others, but nothing out of the ordinary.
Does it matter for this recreation ?
box.log output this every few minutes, so I'm thinking the recreation is ongoing and when it's done it should start the platform following the script directive...
Friday night, saturday, night, sunday, night, Monday morning and it's still printing dots...
2022-09-12T06:53:23.963Z box:locker Lock unreleased platform_start
benborges last edited by
I went and stopped the process, started it all over again but this time I managed to catch that there is a problem with the script right at the beginning, I can't have the log file because I reverted back to my snapshot of Ubuntu 20
But the error is about docker network not being able to get an IP fro the box network and when it try it fails but then continue with the "recreation" of containers as if the previous step had worked properly ?
@benborges It shouldn't take so long to recreate containers. Maybe 3-5 minutes, but that's about it.
Do you have the logs in
/home/yellowtent/platformdata/logs/box.log? Usually, it will have an indication of why things are stuck.
box.log output this every few minutes
the message is displayed to indicate that box code itself is running but something is causing the platform to not start/initialization is not completed. Do you have the logs of above these lines? There will be a
docker run xxxfailing most likely.
benborges last edited by
When I realized I had been waiting for nothing for 4 days I reverted back to snapshot, so now I'm on Ubuntu 20 and I can't find anything.
but it's very clear that the process was going on for ever, without even the docker running (even tho the service was active and loaded)
@benborges Ah ok. Maybe you can wait for 7.3. Please update to that and try to update again and we can debug further. There are some cgroup v2 related fixes for Ubuntu 22 in 7.3 which affect docker container creation, it's possible you hit that case.