diff options
| author | Giuseppe Scrivano <gscrivan@redhat.com> | 2019-03-21 13:38:44 +0100 |
|---|---|---|
| committer | Giuseppe Scrivano <gscrivan@redhat.com> | 2019-03-21 18:53:27 +0100 |
| commit | 927b13dfa5ce1aaa44dd8ac453a0945514eb89ee (patch) | |
| tree | db7deefc00de69b50b4c5b1a808908b8f471822c /troubleshooting.md | |
| parent | 97b966b851dda998e44c0722f10655bd4b911434 (diff) | |
| download | podman-927b13dfa5ce1aaa44dd8ac453a0945514eb89ee.tar.gz podman-927b13dfa5ce1aaa44dd8ac453a0945514eb89ee.tar.bz2 podman-927b13dfa5ce1aaa44dd8ac453a0945514eb89ee.zip | |
troubleshooting: explain setup user: invalid argument
replace an old issue that is not valid anymore, since we support
single UIDs mapped into the namespace.
Closes: https://github.com/containers/libpod/issues/2714
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Diffstat (limited to 'troubleshooting.md')
| -rw-r--r-- | troubleshooting.md | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/troubleshooting.md b/troubleshooting.md index 882afef0c..08d79723a 100644 --- a/troubleshooting.md +++ b/troubleshooting.md @@ -210,18 +210,17 @@ cannot find newuidmap: exec: "newuidmap": executable file not found in $PATH Install a version of shadow-utils that includes these executables. Note RHEL7 and Centos 7 will not have support for this until RHEL7.7 is released. -### 10) podman fails to run in user namespace because /etc/subuid is not properly populated. +### 10) rootless setup user: invalid argument Rootless podman requires the user running it to have a range of UIDs listed in /etc/subuid and /etc/subgid. #### Symptom -If you are running podman or buildah as a user, you get an error complaining about -a missing subuid ranges in /etc/subuid. +An user, either via --user or through the default configured for the image, is not mapped inside the namespace. ``` -podman run -ti fedora sh -No subuid ranges found for user "johndoe" in /etc/subuid +podman run --rm -ti --user 1000000 alpine echo hi +Error: container create failed: container_linux.go:344: starting container process caused "setup user: invalid argument" ``` #### Solution |