Cloudron Forum

Thanks a lot @james !!
I've applied the fix stated in the mentionned post and everything is back to normal !

Hello

Since Friday my cloudron is down, i can't access my dashboard and apps.
When i use troubleshooting it appears that de docker service is down.

Vendor: QEMU Product: Standard PC (i440FX + PIIX, 1996)
Linux: 5.15.0-176-generic
Ubuntu: jammy 22.04
Execution environment: kvm
Processor: AMD EPYC 7543P 32-Core Processor x 4
RAM: 16373052KB
Disk: /dev/sda1       150G
[OK]    node version is correct
[OK]    IPv6 is enabled and public IPv6 address is working
        Docker is down. Trying to restart docker ...
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.

I've checked the log from journal:
First it said the following directives are specified both as a flag and in the configuration file: log-driver: (from flag: journald, from file: json-file)
So i've removed the log-driver flag ("log-driver":"json-file") from /etc/docker/deamon.json.
Now docker still won't run because of a panic.

May 22 08:15:36 srv482015 dockerd[3849338]: time="2026-05-22T08:15:36.186373711Z" level=info msg="Creating a containerd client" address=/run/containerd/containerd.sock timeout=1m0s
May 22 08:15:36 srv482015 dockerd[3849338]: panic: runtime error: invalid memory address or nil pointer dereference
May 22 08:15:36 srv482015 dockerd[3849338]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x55af0a3e82cd]

containerd service is perfectly running, according to Claude the problem comes from containerd and docker incompatible versions :

Docker version 29.1.5, build 3b01d64
containerd containerd.io v2.2.1 dea7da592f5d1d2b7755e3a161be07f43fad8f75

But I'm reaching out to you as those version are supposed to be handled by Cloudron and not modified manually.

Thanks in advance.