Update to 8.0 - Stuck on “removing containers for upgrade”
-
@nichu42 Right...?!?!
-
Ah good to know, thanks for reporting ...
We only staged it late last night
Only update if you feel like an early adopter at this point . -
G girish marked this topic as a question on
-
G girish has marked this topic as solved on
-
I am sure there is some xkcd for this
-
@lukas it showed up for me after manually searching for an update - will wait on updating though. I'm somewhere between the early adopter and early majority groups, so the chasm I guess
-
BTW, love the admin notes that use markdown (previously, I "hid" my notes in the cron tab with a leading "#"...). You can do really helpful stuff....
-
Just to let you guys know that upgrade to 8.0.0 on my Cloudron with 22 Apps did work without problems.
Only thing I noticed was, that I had to re-mount ALL external CIFS drives manually, and therefore had to restart some Cloudron Apps which was using those. -
Just to let you guys know that upgrade to 8.0.0 on my Cloudron with 22 Apps did work without problems.
Only thing I noticed was, that I had to re-mount ALL external CIFS drives manually, and therefore had to restart some Cloudron Apps which was using those.@Kubernetes Yes, same here. Just noticed this morning that the backup had failed because CIFS storage was not mounted.
-
Interesting.. There is nothing inherently in the code that affects mounts. In fact, there is no code to unmount stuff automatically . I will test what is going on. I suspect the issue is with the DNS change. We have moved to systemd-resolved instead of unbound .
-
Hi, we did not initiate an update manually. According to the logs, Cloudron updated to v8.0.3 this morning at 6:58. The message "removing containers for upgrade" was still there at midday. Error message when going to an app: "This app is currently not responding. Please try refreshing the page in a few minutes."
After a manual reboot, all apps were "Configuring (Queued)" for a while. Now the first apps are running again. Yeah
