-
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
Image quay.io/podman/upstream fails on "podman build" when run as root (inside the container) on a RHEL 8.5: msg: modprobe: FATAL: Module ip_tables not found #13294
Comments
You have to load the kernel modules as root on the host. Looking at the containers.conf file in container the default netns value should already be set to host. |
In our case our development machines are shared among all the developers of the company, who don't have any root rights. These machines are being administrated by a small group of "sysadmins", so technically I could ask them to change the global config, but somehow I would expect this scenario to work without changing the host config (as the non root scenario works). |
A friendly reminder that this issue had no activity for 30 days. |
Buildah ignores the container.conf settings. Commit 05d5d22 tried to fix this but I cannot see how this would have worked, there were also no test added related to containers.conf. The code below were we read the default just overwrites everything we already set so the config settings are ignored. Also there are many weird places were settings are just overwritten for no particular reason. The namespaces code path looks like mess to me. Namespaces are added/changed/removed in many different places and there is no explanation why. Maybe I am just not familar enough with this code base but I cannot really understand this. Hopefully a maintainer can take a closer look to see if my changes are indeed correct. Fixes containers/podman#13294 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Buildah ignores the container.conf settings. Commit 05d5d22 tried to fix this but I cannot see how this would have worked, there were also no test added related to containers.conf. The code below were we read the default just overwrites everything we already set so the config settings are ignored. Also there are many weird places were settings are just overwritten for no particular reason. The namespaces code path looks like mess to me. Namespaces are added/changed/removed in many different places and there is no explanation why. Maybe I am just not familar enough with this code base but I cannot really understand this. Hopefully a maintainer can take a closer look to see if my changes are indeed correct. Fixes containers/podman#13294 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Buildah ignores the container.conf settings. Commit 05d5d22 tried to fix this but I cannot see how this would have worked, there were also no test added related to containers.conf. The code below were we read the default just overwrites everything we already set so the config settings are ignored. Also there are many weird places were settings are just overwritten for no particular reason. The namespaces code path looks like mess to me. Namespaces are added/changed/removed in many different places and there is no explanation why. Maybe I am just not familar enough with this code base but I cannot really understand this. Hopefully a maintainer can take a closer look to see if my changes are indeed correct. Fixes containers/podman#13294 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Buildah ignores the container.conf settings. Commit 05d5d22 tried to fix this but I cannot see how this would have worked, there were also no test added related to containers.conf. The code below were we read the default just overwrites everything we already set so the config settings are ignored. Also there are many weird places were settings are just overwritten for no particular reason. The namespaces code path looks like mess to me. Namespaces are added/changed/removed in many different places and there is no explanation why. Maybe I am just not familar enough with this code base but I cannot really understand this. Hopefully a maintainer can take a closer look to see if my changes are indeed correct. Fixes containers/podman#13294 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Buildah ignores the container.conf settings. Commit 05d5d22 tried to fix this but I cannot see how this would have worked, there were also no test added related to containers.conf. The code below were we read the default just overwrites everything we already set so the config settings are ignored. Also there are many weird places were settings are just overwritten for no particular reason. The namespaces code path looks like mess to me. Namespaces are added/changed/removed in many different places and there is no explanation why. Maybe I am just not familar enough with this code base but I cannot really understand this. Hopefully a maintainer can take a closer look to see if my changes are indeed correct. Fixes containers/podman#13294 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Buildah ignores the container.conf settings. Commit 05d5d22 tried to fix this but I cannot see how this would have worked, there were also no test added related to containers.conf. The code below were we read the default just overwrites everything we already set so the config settings are ignored. Also there are many weird places were settings are just overwritten for no particular reason. The namespaces code path looks like mess to me. Namespaces are added/changed/removed in many different places and there is no explanation why. Maybe I am just not familar enough with this code base but I cannot really understand this. Hopefully a maintainer can take a closer look to see if my changes are indeed correct. Fixes containers/podman#13294 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Buildah ignores the container.conf settings. Commit 05d5d22 tried to fix this but I cannot see how this would have worked, there were also no test added related to containers.conf. The code below were we read the default just overwrites everything we already set so the config settings are ignored. Also there are many weird places were settings are just overwritten for no particular reason. The namespaces code path looks like mess to me. Namespaces are added/changed/removed in many different places and there is no explanation why. Maybe I am just not familar enough with this code base but I cannot really understand this. Hopefully a maintainer can take a closer look to see if my changes are indeed correct. Fixes containers/podman#13294 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Buildah ignores the container.conf settings. Commit 05d5d22 tried to fix this but I cannot see how this would have worked, there were also no test added related to containers.conf. The code below were we read the default just overwrites everything we already set so the config settings are ignored. Also there are many weird places were settings are just overwritten for no particular reason. The namespaces code path looks like mess to me. Namespaces are added/changed/removed in many different places and there is no explanation why. Maybe I am just not familar enough with this code base but I cannot really understand this. Hopefully a maintainer can take a closer look to see if my changes are indeed correct. Fixes containers/podman#13294 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Buildah ignores the container.conf settings. Commit 05d5d22 tried to fix this but I cannot see how this would have worked, there were also no test added related to containers.conf. The code below were we read the default just overwrites everything we already set so the config settings are ignored. Also there are many weird places were settings are just overwritten for no particular reason. The namespaces code path looks like mess to me. Namespaces are added/changed/removed in many different places and there is no explanation why. Maybe I am just not familar enough with this code base but I cannot really understand this. Hopefully a maintainer can take a closer look to see if my changes are indeed correct. Fixes containers/podman#13294 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
We are in a company environment, so unfortunately we are stuck with RHEL 8, and don't have access to Fedora. In order to report upstream podman bugs, we want to try with podman upstream first to check if the bug is still present. It used to work, however now with podman 4.0.0 it seems to be broken when podman is run as root inside the container
Steps to reproduce the issue:
Describe the results you received:
Any "podman build" run as root inside the
quay.io/podman/upstream
image involving aRUN
Dockerfile directive will fail when run on a RHEL 8 host.Describe the results you expected:
I would expect the image
quay.io/podman/upstream
to work out of the box on a RHEL 8 host. Most likely some new config wrt the network backend shall be added in https://github.com/containers/podman/blob/main/contrib/podmanimage/stable/containers.conf so that this works by default.Note: it would be really cool if Red Hat provided some "upstream" stream for the "container-tools" module to always be able to install on RHEL machines some unstable but latest podman versions ;)
The text was updated successfully, but these errors were encountered: