diff options
| author | nitrocode <nitrocode@users.noreply.github.com> | 2019-12-08 16:20:53 -0500 |
|---|---|---|
| committer | nitrocode <nitrocode@users.noreply.github.com> | 2019-12-13 20:31:43 -0500 |
| commit | a8460aa0847ebbe320598564827829e8b29ea544 (patch) | |
| tree | 4e9f2df71cedd9277ec58facd32e1158577c022a | |
| parent | 7287f69b52e5bcb59f9977b261ee488942465ecb (diff) | |
| download | podman-a8460aa0847ebbe320598564827829e8b29ea544.tar.gz podman-a8460aa0847ebbe320598564827829e8b29ea544.tar.bz2 podman-a8460aa0847ebbe320598564827829e8b29ea544.zip | |
troubleshooting.md: rebased master and bumped 18 to 19
Signed-off-by: nitrocode <nitrocode@users.noreply.github.com>
| -rw-r--r-- | troubleshooting.md | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/troubleshooting.md b/troubleshooting.md index 9def0e08b..432c0e32b 100644 --- a/troubleshooting.md +++ b/troubleshooting.md @@ -442,3 +442,30 @@ Attempts to run podman result in #### Solution One workaround is to disable Secure Boot in your BIOS. + +### 19) error creating libpod runtime: there might not be enough IDs available in the namespace + +Unable to pull images + +#### Symptom + +```console +$ podman unshare cat /proc/self/uid_map + 0 1000 1 +``` + +#### Solution + +```console +$ podman system migrate +``` + +Original command now returns + +``` +$ podman unshare cat /proc/self/uid_map + 0 1000 1 + 1 100000 65536 +``` + +Reference [subuid](http://man7.org/linux/man-pages/man5/subuid.5.html) and [subgid](http://man7.org/linux/man-pages/man5/subgid.5.html) man pages for more detail.
\ No newline at end of file |