Bug 1730773
Summary: | podman with privileged doesn't provide access to /dev/kvm | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bruno Goncalves <bgoncalv> |
Component: | podman | Assignee: | Giuseppe Scrivano <gscrivan> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 30 | CC: | bbaude, dwalsh, jnovy, lsm5, mheon, pingou |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-26 18:06:34 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: |
Description
Bruno Goncalves
2019-07-17 15:05:43 UTC
Running Podman as a normal user runs with no privileges that the user running does not have. Even --privileged does not change this - it simply restores more of the privileges the user normally has, loosening restrictions on accessing the host system (but still with the privileges of the user running Podman). If the user running Podman does not have access to /dev/kvm, Podman can't do anything about that - the privileges for the device node will still prevent us from accessing it. I suspect that's what's happening here. You're correct that this is poorly documented, though. We need to work on that. I actually think this is a bug in podman. podman run --privileged fedora ls /dev Shows just the limited devices, while as root shows all of the devices. Rootless Podman should basically bind mount all of the devices from /dev into the container. ls -l /dev/kvm crw-rw-rw-. 1 root kvm 10, 232 Jul 17 11:09 /dev/kvm Is accessible by the user. Giuseppe could you look at this? PR opened here: https://github.com/containers/libpod/pull/3593 This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |