opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2025-05-31 15:42:48 +08:00
Code Issues Packages Projects Releases Wiki Activity

Touch up some troubleshooting nits

Browse Source 
Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
This commit is contained in:
TomSweeneyRedHat
2019-01-01 11:36:38 -05:00
parent a634d5559f
commit a25b707fdb
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
troubleshooting.md
View File

@ -86,6 +86,9 @@ could not get runtime: database run root /run/user/1000/run does not match our r
#### Solution
This problem has been fixed in Podman release 0.12.1 and it is recommended
to upgrade to that version. If that is not possible use the following procedure.
To work around the new default path, we can manually set the path Podman is
expecting in a configuration file.
@ -101,7 +104,7 @@ the first path in the error message Podman gave (in this case,
`/run/user/1000/run`).
---
### 4) rootless containers cannot ping hosts
### 5) rootless containers cannot ping hosts
When using the ping command from a non-root container, the command may
fail because of a lack of privileges.
@ -128,9 +131,10 @@ To change its value you can use something like: `sysctl -w
To make the change persistent, you'll need to add a file in
`/etc/sysctl.d` that contains `net.ipv4.ping_group_range=0 $MAX_UID`.
### 5) Build hangs when the Dockerfile contains the useradd command
---
### 6) Build hangs when the Dockerfile contains the useradd command
When the Dockerfile contains a command like RUN useradd -u 99999000 -g users newuser the build can hang.
When the Dockerfile contains a command like `RUN useradd -u 99999000 -g users newuser` the build can hang.
#### Symptom