summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com>2018-11-12 10:34:13 -0800
committerGitHub <noreply@github.com>2018-11-12 10:34:13 -0800
commita4cc7bca60f28fbc43ff9bb203e7f25244017222 (patch)
treef8155c8325bd9694a9df6cb494faec11dae1735a
parent51a1b85fb52721eb5dc2f7847b00f0b0ed811cef (diff)
parent8bda62e06123e0671e38e98560fbb4adbf904faa (diff)
downloadpodman-a4cc7bca60f28fbc43ff9bb203e7f25244017222.tar.gz
podman-a4cc7bca60f28fbc43ff9bb203e7f25244017222.tar.bz2
podman-a4cc7bca60f28fbc43ff9bb203e7f25244017222.zip
Merge pull request #1802 from mheon/troubleshooting_rootless
Update troubleshooting guide to deal with rootless path
-rw-r--r--troubleshooting.md34
1 files changed, 33 insertions, 1 deletions
diff --git a/troubleshooting.md b/troubleshooting.md
index 9d99d5d89..574196a69 100644
--- a/troubleshooting.md
+++ b/troubleshooting.md
@@ -10,7 +10,7 @@
A large number of issues reported against Podman are often found to already be fixed
in more current versions of the project. Before reporting an issue, please verify the
version you are running with `podman version` and compare it to the lastest release
-documented on the top of Podman's [README.md](README.md).
+documented on the top of Podman's [README.md](README.md).
If they differ, please update your version of PODMAN to the latest possible
and retry your command before reporting the issue.
@@ -68,6 +68,38 @@ communicate with a registry and not use tls verification.
* Turn off tls verification by passing false to the tls-verification option.
* I.e. `podman push --tls-verify=false alpine docker://localhost:5000/myalpine:latest`
+
+---
+### 4) Rootless: could not get runtime - database configuration mismatch
+
+In Podman release 0.11.1, a default path for rootless containers was changed,
+potentially causing rootless Podman to be unable to function. The new default
+path is not a problem for new installations, but existing installations will
+need to work around it with the following fix.
+
+#### Symptom
+
+```console
+$ podman info
+could not get runtime: database run root /run/user/1000/run does not match our run root /run/user/1000: database configuration mismatch
+```
+
+#### Solution
+
+To work around the new default path, we can manually set the path Podman is
+expecting in a configuration file.
+
+First, we need to make a new local configuration file for rootless Podman.
+* `mkdir -p ~/.config/containers`
+* `cp /usr/share/containers/libpod.conf ~/.config/containers`
+
+Next, edit the new local configuration file
+(`~/.config/containers/libpod.conf`) with your favorite editor. Comment out the
+line starting with `cgroup_manager` by adding a `#` character at the beginning
+of the line, and change the path in the line starting with `tmp_dir` to point to
+the first path in the error message Podman gave (in this case,
+`/run/user/1000/run`).
+
---
### 4) rootless containers cannot ping hosts