-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Podman 2.2.1 breaks buildah in Podman container. #8712
Comments
Could be #8561 |
A friendly reminder that this issue had no activity for 30 days. |
This is still an issue and so far the workaround is using an old version. |
@jonasbb Any chance you can check this against the main branch? |
@rhatdan I can check it with Fedora Rawhide and a recent build from bodhi. Would that suffice? |
Rawhide should suffice. |
@rhatdan This does not seem fixed yet. Could you re-open the issue, please?
I can re-test after #8949 is available via bodhi. |
This issue is fixed for me in Rawhide with Podman 0.144.dev.git73b036d.fc34 (downloaded from bodhi). So I assume #8949 fixed this issue. Thanks :) |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I use Podman + Buildah in Gitlab CI to build docker images. I use
quay.io/buildah/stable:latest
as the build container and then runbuildah --storage-driver=vfs bud .
in the container to create the image.Steps to reproduce the issue:
Dockerfile
with this content:Start build container:
podman run --rm -v $(pwd):/project:Z -it quay.io/buildah/stable:latest
Change into
/project
folder:cd /project
Run the build:
buildah --storage-driver=vfs bud .
Describe the results you received:
Building the container fails with this error:
journalctl -fxe
reports these SELinux errors in enforcing mode.I switched the Fedora host system to permissive. Then building succeeds with some warnings, yet still SELinux messages in the log:
journalctl -fxe
reports these SELinux errors after switching to permissive mode:Describe the results you expected:
The build should be able to succeed without any warnings printed.
Additional information you deem important (e.g. issue happens only occasionally):
I can reproduce this error reliable. I first noticed the problem on my Fedora 32 machine and then reproduced the results in Fedora 33.
Downgrading the packages
podman
,podman-plugins
andcontainers-common
solves this issue for meShortly before this problem appeared first my system upgraded podman from
podman-2:2.2.1-1.fc32.x86_64
topodman-2:2.2.0-2.fc32.x86_64
. So my best guess is that version 2.2.1 introduced this regression. Unfortunately I do not know how to downgrade to version 2.2.0 to test this.EDIT: I downloaded the podman 2.2.0 packages from here (https://koji.fedoraproject.org/koji/buildinfo?buildID=1648168) and can confirm this version works. The regression is therefore in the 2.2.0 -> 2.2.1 update.
This bug might be related to #8711. However, I see different SELinux messages related to mountin instead of writing.
Output of
podman version
:Fedora 33:
Fedora 32:
Output of
podman info --debug
:Fedora 33:
Fedora 32:
Package info (e.g. output of
rpm -q podman
orapt list podman
):Fedora 33:
Fedora 32:
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: