Bug#989317: systemd kill background processes after user logs out (#825394 regression)
Michael Biebl
biebl at debian.org
Tue Jun 8 15:19:16 BST 2021
Control: tags -1 + unreproducible
So, I've been following the instructions in
/usr/share/doc/lxc/README.Debian to allow unprivileged containers.
After that, I could successfully run a container. I used the command
line as suggested in that README.Debian:
$ systemd-run --scope --quiet --user --property=Delegate=yes \
lxc-start -n mycontainer
Once I logged out, the systemd --user session was stopped including the
container, which is expected, as ansgar wrote.
After enabling "linger" for that user, the systemd --user session was
not stopped anymore after logging out and the container continued running.
I'm thus marking this bug report as unreproducible.
(note that the lxc maintainers recommend to use --scope with systemd-run)
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20210608/0b3dab4d/attachment.sig>
More information about the Pkg-systemd-maintainers
mailing list