FS#55983 - [systemd] systemd-nspawn --bind loses mount

Attached to Project: Arch Linux
Opened by Christian Rebischke (Shibumi) - Friday, 13 October 2017, 17:53 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 19 October 2017, 13:44 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I have a systemd-nspawn container with the following override.conf:

ExecStart=/usr/bin/systemd-nspawn --quiet --keep-unit --boot --link-journal=try-guest --settings=override --machine=%I --capability=CAP_NET_ADMIN --network-veth --bind=/tmp/.X11-unix:/tmp/.X11-unix --setenv="DISPLAY=:0"


I had no issues in the last releases with this setup, but with systemd 235-1 the --bind doesn't seem to work anymore. When I start the container via `machinectl start <containername>` the directory is suddenly empty and when I stop the container it remainds empty.

When I check for `/tmp/.X11-unix/X0` via `lsof`. I can see the following:

Xorg 673 674 chris 43u unix 0xffff97a489ffdc00 0t0 118253 @/tmp/.X11-unix/X0 type=STREAM

looks like the stream is still there but isolated from the rest of the filesystem.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Thursday, 19 October 2017, 13:44 GMT
Reason for closing:  Upstream
Comment by Christian Rebischke (Shibumi) - Saturday, 14 October 2017, 13:16 GMT
Upstream Bug-Report: https://github.com/systemd/systemd/issues/7093

Loading...