Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1746364
Summary: | applying cgroup configuration for process caused \"mountpoint for devices not found\"": OCI runtime error | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Lukas Slebodnik <lslebodn> |
Component: | podman | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 31 | CC: | awilliam, bbaude, dustymabe, dwalsh, frantisek.kluknavsky, jnovy, lsm5, mheon, santiago |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | AcceptedFreezeException | ||
Fixed In Version: | podman-1.5.1-2.17.dev.gitce64c14.fc31 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-09-03 21:30:40 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1644938 |
Description
Lukas Slebodnik
2019-08-28 09:31:42 UTC
I know there is a workaround with kernel comandline option (systemd.unified_cgroup_hierarchy=0) But I would like to be notified when I can revert that workaround. And I hope it will be also fixed in f31 but I used rawhide which usually contains latest podman from upstream. You need to change default oci runtime to crun in /etc/containers/libpod.conf I updated podman-1.5.1-2.17.dev.gitce64c14.fc31 yesterday to change the default. Please try this out and see if it fixes the issue. And then update the karma https://bodhi.fedoraproject.org/updates/FEDORA-2019-0a601cf11c Sanity checks passed for me. podman-1.5.2-0.36.dev.git1eb6b27.fc32.x86_64 podman-1.5.1-2.17.dev.gitce64c14.fc31.x86_64 But it is already after beta freeze https://fedoraproject.org/wiki/Releases/31/Schedule So you might consider request an exception for this BZ. How do I request an exception? Fixed in podman-1.5.2-0.36.dev.git1eb6b27.fc32.x86_64 (In reply to Daniel Walsh from comment #4) > How do I request an exception? Go to the blocker bugs application and sign in with your FAS ID and fill out the form: https://qa.fedoraproject.org/blockerbugs/ The bug also needs to be open, or else it won't show up on any of the searches we use. It's worth noting that podman-1.5.1-2.17.dev.gitce64c14.fc31.x86_64 fixes another problem for me. With current podman: ``` [vagrant@vanilla-f31 ~]$ GODEBUG=tls13=0 podman run --rm -it registry.fedoraproject.org/fedora:30 Trying to pull registry.fedoraproject.org/fedora:30... Getting image source signatures Copying blob e214a48be34a done Copying config 1cabdcebde done Writing manifest to image destination Storing signatures Error: systemd cgroup flag passed, but systemd support for managing cgroups is not available: OCI runtime error ``` With `podman-1.5.1-2.17.dev.gitce64c14.fc31.x86_64` this is fixed: ``` [vagrant@vanilla-f31 ~]$ GODEBUG=tls13=0 podman run --rm -it registry.fedoraproject.org/fedora:30 Trying to pull registry.fedoraproject.org/fedora:30... Getting image source signatures Copying blob e214a48be34a done Copying config 1cabdcebde done Writing manifest to image destination Storing signatures [root@0cb217550091 /]# ``` @Dan - I'll handle the blocker justification Proposed as a Freeze Exception for 31-beta by Fedora user mheon using the blocker tracking app because: Podman will not be prepared for the CGroups V2 feature unless this bug is addressed. Almost all container functionality is broken in the present build. FEDORA-2019-0a601cf11c has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-0a601cf11c +1 FE at least for me, while we kick around the criteria proposal. Discussed at today's freeze exception review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2019-09-03/f31-blocker-review.2019-09-03-16.01.html . Accepted as a freeze exception as we consider podman a key component these days and want it to work out of the box if possible. podman-1.5.1-2.17.dev.gitce64c14.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. |