[Solved] Cloudron down after Ubuntu/Docker update (Docker service fails to start)

[james]

Hello @osobo
Do I understand it correct that you did a manual system update and this was not an unattended security update?

[Valexico]

Hi @james
In my case i Didn't do any manual update : I let cloudron manage updates I just schedule a reboot once a week

[osobo]

Hello @james. I think so. Following Cloudron’s notification to reboot the server I’ve simply clicked on the « reboot » link within the dashboard and lost the access from there.

[james]

Hello @valexico and @osobo
Thanks for that.
Can you two please ssh into your Cloudron server and post the output of following command?

docker --version

[osobo]

@james Docker version 29.1.5, build 0e6fee6

[Valexico]

Same here
Docker version 29.1.5, build 0e6fee6

[james]

Hello @osobo and @valexico
Thanks.
Do you still have the /etc/systemd/system/docker.service.d/cloudron.conf file?
Because on two of my Cloudron systems it is also Docker version 29.1.5, build 0e6fee6 and there was no issue with docker.

[Valexico]

No I deleted the file to fix the issue as described by @osobo

[Valexico]

my claude chat if it helps
https://claude.ai/share/acd62c73-b4e5-4e49-9e84-7e06d4229815

[osobo]

Same here. The file has been deleted with the fix.

[jdbaker]

For what its worth, the issue occurred for me last Thursday night after using the reboot option in the dashboard, as instructed by the typical Cloudron notification. The VPS came back up, but the Cloudron dashboard was unreachable. In the VPS terminal, the troubleshooter showed docker was not starting. Two additional VPS reboots did not resolve it, so I simply rolled back, and then everything appeared to be working.

Later that night, Cloudron updated from 9.1.5 to 9.1.6.

When another reboot notification appeared yesterday, I took another snapshot of the VPS before rebooting, and everything came back up just fine.

However, I did NOT delete my cloudron.conf file, and it still exists.

My docker version is 29.1.5, build 0e6fee6.

[Valexico]

@james
So, should we do something to restore our cloudron to nominal configuration ? Recreate this cloudron.conf file somehow ?

[james]

Hello @valexico

@Valexico said:

So, should we do something to restore our cloudron to nominal configuration ? Recreate this cloudron.conf file somehow ?

That would be best I think.
If this would reproduce the previous issue, that be interesting to get an understanding what is causing this.

The default content from /etc/systemd/system/docker.service.d/cloudron.conf is:

[Service]
ExecStart=
ExecStart=/usr/bin/dockerd -H fd:// --log-driver=journald --exec-opt native.cgroupdriver=cgroupfs --storage-driver=overlay2 --experimental --ip6tables --userland-proxy=false