Cloudron down after Ubuntu/Docker update (Docker service fails to start)
-
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 on
-
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,
I am experiencing the same issue, which appeared suddenly. I have tried the different fixes suggested in this thread, but none of them really worked.
Last night, I was able to restart the server and everything seemed to be working fine. However, this morning when I checked again, the system was unresponsive once more.
I am currently traveling for the next 10 days, away from my office, and I only have an iPad with me. I connect to a computer at my office remotely, and from there I access my Cloudron. However, the internet connection where I am is very unstable, which makes troubleshooting extremely difficult.
Thank you in advance for any help you can provide.
Best regards,
Philippe -
This was fixed in support. The system had a file
/etc/docker/daemon.jsonwhich also specified the log-driver causing docker to refuse to start. Simple removing that file and restarting docker brought the system back. -
J james referenced this topic on
-
Greetings, all. My server is upgraded to 9.1.7 on Hostinger. I woke up to find that it was down; perhaps this occurred during the automatic upgrade. There was an error on the dashboard:
Platform startup failed Failed to start services. Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?I saw @nebulon's last post and removed the
daemon.jsonfile. Then restarted the server. It was a longer than usual reboot process, especially hanging for a few minutes on restarting Redis. But eventually all the apps got up and running.Should I be concerned that this might happen again? Or should it be smoother from now on?
-
Greetings, all. My server is upgraded to 9.1.7 on Hostinger. I woke up to find that it was down; perhaps this occurred during the automatic upgrade. There was an error on the dashboard:
Platform startup failed Failed to start services. Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?I saw @nebulon's last post and removed the
daemon.jsonfile. Then restarted the server. It was a longer than usual reboot process, especially hanging for a few minutes on restarting Redis. But eventually all the apps got up and running.Should I be concerned that this might happen again? Or should it be smoother from now on?
-
Hello everyone. Glad the issue is now fixed.
FYI I've received yesterday a legit notification from Hostinger mentioning the following:
**Linux kernel vulnerability disclosed (CVE-2026-31431)** A security flaw called "Copy Fail" (CVE-2026-31431) has been found in the Linux kernel. It affects nearly all major Linux distributions – including Ubuntu, Debian, RHEL, Amazon Linux, SUSE, Fedora, and more – on any kernel built between 2017 and today. The vulnerability lets a local user gain full admin access to a server. It can also affect containerized environments. The fix takes just a few minutes. Option 1: Update your kernel (recommended) For Ubuntu/Debian: sudo apt update, sudo apt upgrade -y For RHEL-based systems: sudo yum update Then reboot your server. Option 2: Disable the affected module (temporary fix) If updating right now isn't an option, disable the vulnerable module to reduce exposure: echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf rmmod algif_aead 2>/dev/null || true This won't affect SSH, TLS, LUKS, or OpenSSL."I'm wondering. Is this issue already addressed by Cloudron's latest updates or should I apply the fix myself ?
Thanks for your support and happy workers' Day
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