-
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
No subuid ranges found for user "<username>" executing any podman command #1182
Comments
Can you check the /etc/subuid file to see if their are entries for your user? If this user account has been around for years, then you will have to manually add entries to this file. grep dwalsh /etc/subuid |
The error message could be better and does the man page tell you anything? |
@giuseppe PTAL |
Improve the error message telling the user where to look for. Closes: containers/podman#1182 Signed-off-by: Giuseppe Scrivano <[email protected]>
in the man page we explicitly say the user must be present in the files We probably need to make this error message clearer as many users will hit it, it is coming from containers/storage: https://github.com/containers/storage/blob/master/pkg/idtools/idtools.go#L142-L147. PR here: containers/storage#204 |
@rhatdan @giuseppe I added the subuids and subgids for the user and they tried again but hit different error now. I also think in the man page if possible to put how to add subuids and subgids if users face issue.
|
how does your /etc/subuid file look now? I think busybox needs more uids than you currently have mapped |
@praveenkumar please manually edit your file and add enough user, |
@giuseppe after manually updating the range size now able to pull the images. |
thanks for confirming it. I am going to close this issue as we already are dealing with improving the documentation and the error message |
I'm running into this same issue. I've executed the commands to setup my subuid and subgid files and have confirmed that they have my username:10000:65536 in them. My uid is 1832001200.
Version of podman
|
Found a solution at #2542.
after modifying my sub*uid files fixed it. |
@jschewebbn You've been my saviour! Works like a charm! |
Awesome! Thank you.. |
I just have to add my own insights, I came across this thread on Google as I'm sure many others will. First of all usermod --add-subuid specifies a range, but /etc/subuid shows a starting value and a max value. So usermod --add-subuid 200000-265535 becomes 200000:65536 in subuid file. Secondly I follow a pattern where I create a user for each container service I want to host, for separation and to avoid root. So I create an elasticsearch user for example, add its subuid and subgid. But this is not enough, all processes of the user must be killed first. In my case there was a lingering podman process belonging to the elasticsearch user even after the users shell had exited. |
The |
This was a great help for my problem. After changing the account name (using usermod) the ole account name has been left unchanged in the /etc/subuid file. |
Might want to open an issue with shadow-utils. This should at least warn you of it. |
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
Description
Steps to reproduce the issue:
podman version
Describe the results you received:
Describe the results you expected:
Version info for podman.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info
:Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: