Summary

Pull request #6979 should be reconsidered because it breaks a useful systemd-nspawn convention for little practical benefit.

See: #6979 (comment)

Submission type

• Bug report

systemd version the issue has been seen with

235

Used distribution

Arch Linux

In case of bug report: Expected behaviour you didn't see

1. Launch container with systemd-nspawn … --bind=/tmp/.X11-unix

2. Run an X client program successfully from within the container.

In case of bug report: Unexpected behaviour you saw

1. Launch container with systemd-nspawn … --bind=/tmp/.X11-unix

2. X client program exits with cannot open display: :0.

3. X unix socket at /tmp/.X11-unix/X0 on the host has been deleted by systemd-nspawn.

In case of bug report: Steps to reproduce the problem

0. Create a container if necessary.

1. Ensure host machine is running an X server that is listening on a unix socket in /tmp/.X11-unix/

2. Boot the container with:

systemd-nspawn --boot --directory DIR --bind=/tmp/.X11-unix

3. Check /tmp/.X11-unix/ in the host and notice that all sockets in the directory have been deleted.