Hi James,
Here are all the details I have so far.
Cloudron environment:
Vendor: QEMU Product: Standard PC
Linux: 6.8.0-111-generic
Ubuntu: noble 24.04
Cloudron: 9.1.7
Execution environment: kvm
Processor: AMD EPYC 9354P 32-Core Processor
BIOS: pc-i440fx-11.0
RAM: 8131480KB
Disk: /dev/sda1 53G
Output of cloudron-support --troubleshoot:
[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.
Output of systemctl status docker.service:
docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; preset: enabled)
Drop-In: /etc/systemd/system/docker.service.d/cloudron.conf
Active: failed (Result: exit-code) since Wed 2026-05-20 06:24:24 UTC; 3 days ago
TriggeredBy: docker.socket
Main PID: 1480807 (code=exited, status=1/FAILURE)
docker.service: Scheduled restart job, restart counter is at 3.
docker.service: Start request repeated too quickly.
docker.service: Failed with result 'exit-code'.
Failed to start docker.service - Docker Application Container Engine.
Output of journalctl -xeu docker.service:
dockerd[1480807]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives are specified both as a flag and in the configuration file: log-driver: (from flag: journald, from file: json-file)
docker.service: Main process exited, code=exited, status=1/FAILURE
docker.service: Failed with result 'exit-code'.
Failed to start docker.service - Docker Application Container Engine.
docker.service: Start request repeated too quickly.
So Docker cannot start because log-driver seems to be defined twice:
as a systemd flag: journald
in /etc/docker/daemon.json: json-file
Cloudron is already on 9.1.7, but Docker is down.
What is the safest Cloudron-compatible fix here without data loss?
Should I remove the log-driver entry from /etc/docker/daemon.json, or should the Cloudron systemd override be changed?
Thanks.