-
Notifications
You must be signed in to change notification settings - Fork 786
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
Error during unshare(CLONE_NEWUSER): Invalid argument error parsing PID (RHEL8) #4087
Comments
Looks like you are running it in some kind of container or some place without the unshare SYSCALL. |
That's the weird part- I've seen a lot of similar issues on this github and RH documentation which indeed state that is the problem but this is running directly on a RHEL VM. Also, it seems stuff like Any additional information I can provide to verify? |
Does |
Alas, both commands return the same thing. Added
|
The issue was resolved by reinstalling the dnf module container-tools |
Please ignore my previous comment as I diagnosed with the wrong user, the issue was not resolved |
Do you have any monitoring agent like Dynatrace(dynatrace modules configured to load via /etc/ld.so.preload) on the node ?. If yes, can you try disabling the preload and check |
@rhatdan I opened a case with RedHat support and the root cause is a Dynatrace OneAgent lib injection (full stack monitoring feature ):
This seems to conflict only sometimes. |
You may have to follow it up with Dynatrace to understand why it is blocking the unshare syscall ? |
Well, the case contains an strace and at this point I cannot determine whether a fix would be needed in buildah or a fix would be needed in the dynatrace oneagent as I don't have the necessary expertise to troubleshoot syscalls, so I thought I'd inform both parties. |
Looks like you are running buildah in a rootless enviroment, which will trigger it to unshare to setup the user namespace. Have you tried to run it as root inside of the container? |
It seems like you did not read the latest comments but no matter, the issue is resolved. For anyone experiencing the same issue:
|
Description
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
buildah info to run successfully:
Output of
rpm -q buildah
orapt list buildah
:Output of
buildah version
:Output of
podman version
if reporting apodman build
issue:Output of
cat /etc/*release
:Output of
uname -a
:Output of
cat /etc/containers/storage.conf
:(removed comments, hostnames)
Additional info:
cat /etc/subuid
jenkins:296608:65536
cat /etc/subgid
jenkins:296608:65536
grep CONFIG_USER_NS /boot/config-$(uname -r)
CONFIG_USER_NS=y
capsh --print
We have another node with the same setup where buildah works fine. Not sure where else to look at this point.
Please let me know if additional info is required.
The text was updated successfully, but these errors were encountered: