-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[2.0 regression] /sys/fs/{selinux,cgroup} no longer masked during build (not reproducible with buildah) #6879
Comments
I am not seeing this?
$ podman build --no-cache /tmp $ sudo podman build --no-cache /tmp podman --version |
Ok I see it now, in rootless mode you are getting an error listing /sys/fs/selinux |
I'm sorry I failed to mention I am indeed running rootless. |
Comparing the output between podman and buildah, it looks like the cgroups mount point is not hidden anymore:
|
I have, I think, the opposite problem. With rootless podman 2.0.2, I have rw access to
The fix for this is to make |
Reproducer:
|
This is fixed in buildah with 7b928d0dea016ae5f26b058cb0d8b68e6789cad0 |
@TomSweeneyRedHat We need to vendor and updated buidlah 1.15 branch into podman. |
@rhatdan let's chat during scrum about the specifics and I'll get stuff under way Monday afternoon. |
Any update on this? Thanks |
I believe this is fixed in podman 2.0.5 or earilier. |
I just checked podman 2.0.5 and it seems to be fixed. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
During builds with the podman 2.0+ releases, the
/sys/fs/selinux
folder is not masked with an empty root:root 777 directory, confusing yum//dnf into thinking that it should do SELinux related setup which will fail.This does not happend with podman
2:1.8.2-2.fc32
, but only with podman2:2.0.1-1.fc32
.The following Containerfile builds successfully with buildah
1.15.0-1.fc32
& podman2:1.8.2-2.fc32
:But fails with podman
2:2.0.1-1.fc32
.Steps to reproduce the issue:
podman build --no-cache .
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
Physical Fedora 32 Workstation.
The text was updated successfully, but these errors were encountered: