Cloudron down after Ubuntu/Docker update (Docker service fails to start)
-
Thanks for the access @valexico . The issue has to do with the faulty ubuntu kernel update . Updating the firewall makes it work.
Technical details: Cloudron configures docker and containers to log using the syslog service (cloudron-syslog) . Because of the kernel regression, docker is unable to reach the syslog service and doesn't start anymore. The cgroupfs was not the issue.
We are making a patch release for Cloudron which fixes the firewall rules .
-
J joseph has marked this topic as solved
-
Thanks for the access @valexico . The issue has to do with the faulty ubuntu kernel update . Updating the firewall makes it work.
Technical details: Cloudron configures docker and containers to log using the syslog service (cloudron-syslog) . Because of the kernel regression, docker is unable to reach the syslog service and doesn't start anymore. The cgroupfs was not the issue.
We are making a patch release for Cloudron which fixes the firewall rules .
-
Just experienced this today. Also on Hostinger. Requested reboot and system will not come back online. Have not applied the fix yet so if you want a system that is still broken and you want to investigate, let me know.
@AndyCPNW please check the ubuntu kernel versions. It's 110 probably?
The quick fix:
- Edit
/etc/systemd/system/docker.service.d/cloudron.conf. Change--log-driver=json-file. systemctl daemon-reloadandsystemctl restart docker box
Cloudron 9.1.7 is being rolled out. You can update once the system is up and it will fix the firewall.
- Edit
-
@AndyCPNW please check the ubuntu kernel versions. It's 110 probably?
The quick fix:
- Edit
/etc/systemd/system/docker.service.d/cloudron.conf. Change--log-driver=json-file. systemctl daemon-reloadandsystemctl restart docker box
Cloudron 9.1.7 is being rolled out. You can update once the system is up and it will fix the firewall.
@joseph Thanks - I tried the cloudron-firewall.sh patch and restarting but did not get docker to come up so I deleted the conf file like the original solution suggested and it came right back again. Yes it was kernel 110. Everything seems to be running now. Bummer that kernel upgrade caused all of this. Thanks for the help.
- Edit
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better ๐
Register Login