Closed Cyborgscode closed 4 years ago
Fix (more a workaround):
add "systemd.unified_cgroup_hierarchy=0" the kernel line and reboot.
Or switch to podman for Fedora.
just commenting to say changing to podman instead of docker fixed the issue for me. Thanks Cyborgscode
is it fixed now or why did you close it?
A solution was provided, so I was under the impression that was the end of it. Also, we don't support podman.
it's just a workround, not a solution. But as Docker has to fix this issue, you can't do much.
System got upgraded from Fedora 30 to Fedora31. On first startup docker pulled a shitload of new data in, but failed to start the containers:
]# docker-compose up -d Creating network "docker-jitsi-meet_meet.jitsi" with the default driver Creating docker-jitsi-meet_prosody_1 ... error Creating docker-jitsi-meet_web_1 ...
Creating docker-jitsi-meet_web_1 ... error
ERROR: for docker-jitsi-meet_web_1 Cannot start service web: OCI runtime create failed: this version of runc doesn't work on cgroups v2: unknown
ERROR: for prosody Cannot start service prosody: OCI runtime create failed: this version of runc doesn't work on cgroups v2: unknown
ERROR: for web Cannot start service web: OCI runtime create failed: this version of runc doesn't work on cgroups v2: unknown ERROR: Encountered errors while bringing up the project.
How can we fix this?