<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[[Solved] Cloudron down after Ubuntu&#x2F;Docker update (Docker service fails to start)]]></title><description><![CDATA[<p dir="auto">Hello all,</p>
<p dir="auto">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.</p>
<p dir="auto">After applying recent Ubuntu security updates and rebooting, my Cloudron instance became unreachable.</p>
<pre><code>cloudron-support --troubleshoot
</code></pre>
<p dir="auto">showed Docker was down, and</p>
<pre><code>systemctl start docker
</code></pre>
<p dir="auto">failed while running dockerd manually worked fine.</p>
<p dir="auto">I've worked it out with the support of ChatGPT. Root cause : An outdated Cloudron systemd override file:</p>
<pre><code>/etc/systemd/system/docker.service.d/cloudron.conf
</code></pre>
<p dir="auto">This 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.</p>
<p dir="auto">Fix : Remove the override and reload systemd:</p>
<pre><code>sudo rm /etc/systemd/system/docker.service.d/cloudron.conf
sudo systemctl daemon-reexec
sudo systemctl daemon-reload
sudo systemctl restart docker
</code></pre>
<p dir="auto">Verify Docker is running:</p>
<pre><code>systemctl status docker
</code></pre>
<p dir="auto">Then restart Cloudron:</p>
<pre><code>sudo systemctl restart box
</code></pre>
<p dir="auto">Result</p>
<p dir="auto">Docker starts normally again, containers come back up, and the Cloudron dashboard becomes accessible.</p>
<p dir="auto">Notes<br />
Modern Docker versions already handle most of the options that the override was forcing.<br />
Removing the override lets Docker run with its correct defaults (including proper cgroup handling).<br />
This issue may appear after unattended upgrades or manual system updates.</p>
<p dir="auto">Hope this helps anyone running into the same issue <img src="https://forum.cloudron.io/assets/plugins/nodebb-plugin-emoji/emoji/android/1f44d.png?v=16ee7d1409f" class="not-responsive emoji emoji-android emoji--+1" style="height:23px;width:auto;vertical-align:middle" title="👍" alt="👍" /></p>
]]></description><link>https://forum.cloudron.io/topic/15417/solved-cloudron-down-after-ubuntu-docker-update-docker-service-fails-to-start</link><generator>RSS for Node</generator><lastBuildDate>Sun, 19 Apr 2026 14:51:43 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/15417.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 19 Apr 2026 11:06:49 GMT</pubDate><ttl>60</ttl></channel></rss>