opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2025-08-06 19:44:14 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #6082 from TomSweeneyRedHat/dev/tsweeney/trub1

Browse Source 
[CI:DOC] Add linger to troubleshooting
This commit is contained in:
OpenShift Merge Robot
2020-05-05 10:23:30 +02:00
committed by GitHub
parent 01aad516e0 fa3986125e
commit e1be837a4f
1 changed files with 20 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
troubleshooting.md
View File

@ -517,3 +517,23 @@ The runtime uses `setgroups(2)` hence the process looses all additional groups
the non-root user has. If you use the `crun` runtime, 0.10.4 or newer, the non-root user has. If you use the `crun` runtime, 0.10.4 or newer,
then you can enable a workaround by adding `--annotation io.crun.keep_original_groups=1` then you can enable a workaround by adding `--annotation io.crun.keep_original_groups=1`
to the `podman` command line. to the `podman` command line.
### 22) A rootless container running in detached mode is closed at logout
When running a container with a command like `podman run --detach httpd` as
a rootless user, the container is closed upon logout and is not kept running.
#### Symptom
When logging out of a rootless user session, all containers that were started
in detached mode are stopped and are not kept running. As the root user, these
same containers would survive the logout and continue running.
#### Solution
When systemd notes that a session that started a Podman container has exited,
it will also stop any containers that has been associated with it. To avoid
this, use the following command before logging out: `loginctl enable-linger`.
To later revert the linger functionality, use `loginctl disable-linger`.
LOGINCTL(1), SYSTEMD(1)