diff options
| author | Abhijeet Kasurde <akasurde@redhat.com> | 2022-03-25 16:22:42 +0530 |
|---|---|---|
| committer | Abhijeet Kasurde <akasurde@redhat.com> | 2022-03-25 16:22:42 +0530 |
| commit | 4f73cf3fc7977de5ef005ab92cec6f36f43a617c (patch) | |
| tree | 2533b623144c4d06dca3ce99812cbc6dcac0dc7d | |
| parent | 206dcd48e99d6e60c3b649f60143473f8f602505 (diff) | |
| download | podman-4f73cf3fc7977de5ef005ab92cec6f36f43a617c.tar.gz podman-4f73cf3fc7977de5ef005ab92cec6f36f43a617c.tar.bz2 podman-4f73cf3fc7977de5ef005ab92cec6f36f43a617c.zip | |
Misc typo fixes
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
| -rw-r--r-- | troubleshooting.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/troubleshooting.md b/troubleshooting.md index f59963271..941d1a322 100644 --- a/troubleshooting.md +++ b/troubleshooting.md @@ -912,7 +912,7 @@ Error: error creating tmpdir: mkdir /run/user/1000: permission denied #### Solution -Podman expects a valid login session for the `rootless+cgroupv2` use-case. Podman execution is expected to fail if the login session is not present. In most cases, podman will figure out a solution on its own but if `XDG_RUNTIME_DIR` is pointing to a path that is not writable execution will most fail. Typical scenarious of such cases are seen when users are trying to use Podman with `su - <user> -c '<podman-command>`, or `sudo -l` and badly configured systemd session. +Podman expects a valid login session for the `rootless+cgroupv2` use-case. Podman execution is expected to fail if the login session is not present. In most cases, podman will figure out a solution on its own but if `XDG_RUNTIME_DIR` is pointing to a path that is not writable execution will most fail. Typical scenarios of such cases are seen when users are trying to use Podman with `su - <user> -c '<podman-command>`, or `sudo -l` and badly configured systemd session. Alternatives: @@ -1108,7 +1108,7 @@ ls: cannot open directory '/dir1': Permission denied #### Solution -We follow essentialy the same solution as in the previous +We follow essentially the same solution as in the previous troubleshooting tip: "_Container creates a file that is not owned by the regular UID_" but for this problem the container UID and GID can't be as |