question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

OCI runtime create failed: this version of runc doesn't work on cgroups v2: unknown

See original GitHub issue

I am running Fedora 32, when I execute mvn k8s:build, I get this error: [ERROR] Failed to execute goal org.eclipse.jkube:kubernetes-maven-plugin:1.0.0-alpha-4:build (default-cli) on project codename: Failed to execute the build: Error while trying to build the image: Unable to build image [codename:0.0.1-SNAPSHOT] : "OCI runtime create failed: this version of runc doesn't work on cgroups v2: unknown" -> [Help 1]

I found a similar issue mentioned in another project, which suggest using podman. So at the end of the day, this may just be a +1 for https://github.com/eclipse/jkube/issues/66 because there may not be much else you can do. https://github.com/jitsi/docker-jitsi-meet/issues/618

At any rate, submitting for the review of those that understand all these moving pieces better than I.

I also found https://github.com/geerlingguy/ansible-role-docker/issues/186 which suggests that the true problem may be an issue with the underlying docker-compose with the version of Fedora I am using.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:7 (1 by maintainers)

github_iconTop GitHub Comments

24reactions
dcrissmancommented, Jul 17, 2020

Then I will close this issue out. Thanks for taking a look.

For anyone in the future, I ran the following command on my localhost fedora instance, and it seems to have resolved the issue. sudo grubby --update-kernel=ALL --args="systemd.unified_cgroup_hierarchy=0"

That said, I am uncertain of the consequences of this change, aside from it forced an older version of cgroup. So be warned.

10reactions
netoptimizercommented, Dec 11, 2020

For anyone in the future, I ran the following command on my localhost fedora instance, and it seems to have resolved the issue. sudo grubby --update-kernel=ALL --args="systemd.unified_cgroup_hierarchy=0"

I came here in “the future” via a Google search, thanks. I just want to mention that I solved my problem by using the podman command instead of docker command to start the docker container image.

Read more comments on GitHub >

github_iconTop Results From Across the Web

1885433 – docker: oci runtime create failed / runc doesnt work ...
Hi, Sadly, moby-engine is not yet compatible with cgroups v2, which is used by default by Fedora since Fedora 31 (actually, the error...
Read more >
How To Install Docker On Fedora 32 Or 31 (And Alternatives)
Fedora 32 and 31 switched to cgroup v2, and due to this Docker no longer works. This article explains your options, and how...
Read more >
Docker not working under fedora 32 : r/linuxquestions - Reddit
docker: Error response from daemon: OCI runtime create failed: this version of runc doesn't work on cgroups v2: unknown.
Read more >
Error response from daemon: failed to create shim task: OCI ...
After solving this Circleci local execute --job test-android fails because of missing android:2021.10.1 image, is it from docker hub? - #2 ...
Read more >
exec failed: unable to start container process: open /dev/pts/0 ...
2 Answers 2 ... This issue may relate to docker, first drain your node. ... Second, SSH to the node and restart docker...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found