Closed spitzlei closed 8 months ago
We only support cgroups v1 for now and I think your host machine has cgroups v2. Can you follow these instructions to change back to v1 and see if that works?
cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-6.1.0-17-amd64 root=/dev/mapper/vg0-root ro systemd.unified_cgroup_hierarchy=0 cgroup_enable=memory swapaccount=1 quiet
I'm already running with cgroup v1 (and the system worked like that until the recent docker upgrades from 21.01.2024).
Hmmmm, then we need to investigate... We need to check if they maybe mount the cgroup folder differently.
I had the same issue after upgrading Docker, but https://github.com/DOMjudge/domjudge/pull/2317 seems to fix it. Can you verify by any chance?
Description of the problem
Since the update to docker 24.0.7 the judgehost container fails to start. No change in docker 25.0.0
Your environment
Steps to reproduce
/sys/fs/cgroup:/sys/fs/cgroup:ro
Expected behaviour
Judgehosts should run.
Actual behaviour
Container exits with message above.