Cloudron down after Ubuntu/Docker update (Docker service fails to start)
-
hi @james
Here the status on my fixed (
cloudron.confdeleted). I can't check with the error as this server is used in production... I would have to test at night this not very convenientsystemctl status cloudron-syslog.service WARNING: terminal is not fully functional Press RETURN to continue ● cloudron-syslog.service - Cloudron Syslog Loaded: loaded (/etc/systemd/system/cloudron-syslog.service; enabled; preset: enabled) Active: active (running) since Mon 2026-04-20 20:20:34 UTC; 12h ago Main PID: 734 (MainThread) Tasks: 11 (limit: 19092) Memory: 71.9M (peak: 72.4M) CPU: 9.000s CGroup: /system.slice/cloudron-syslog.service └─734 node /home/yellowtent/box/syslog.js -
Hello @valexico
Can you check if the sock file does really not exist?/home/yellowtent/platformdata/logs/syslog.sock -
Hello @valexico
Can you check if the sock file does really not exist?/home/yellowtent/platformdata/logs/syslog.sock -
Hello all,
Just wanted to share what happened to me and the way to fix it in case you experience the same issue. @cloudron_admin please delete the post if not relevant.
After applying recent Ubuntu security updates and rebooting, my Cloudron instance became unreachable.
cloudron-support --troubleshootshowed Docker was down, and
systemctl start dockerfailed while running dockerd manually worked fine.
I've worked it out with the support of ChatGPT. Root cause : An outdated Cloudron systemd override file:
/etc/systemd/system/docker.service.d/cloudron.confThis override replaces Docker’s default ExecStart and uses older flags (like cgroupfs) that are no longer compatible with newer Docker versions. As a result, Docker fails to start via systemd.
Fix : Remove the override and reload systemd:
sudo rm /etc/systemd/system/docker.service.d/cloudron.conf sudo systemctl daemon-reexec sudo systemctl daemon-reload sudo systemctl restart dockerVerify Docker is running:
systemctl status dockerThen restart Cloudron:
sudo systemctl restart boxResult
Docker starts normally again, containers come back up, and the Cloudron dashboard becomes accessible.
Notes
Modern Docker versions already handle most of the options that the override was forcing.
Removing the override lets Docker run with its correct defaults (including proper cgroup handling).
This issue may appear after unattended upgrades or manual system updates.Hope this helps anyone running into the same issue
-
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 .
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