Bug#993248: machinectl fails to bind mount a directory into a container

[Michael Biebl]

Control: fixed -1 249.3-4

Am 29.08.21 um 12:31 schrieb shilin.aleksej at gmail.com:
> Package: systemd-container
> Version: 247.3-6
> 
> Hi,
> 
> machinectl seems to always fail when trying to bind mount a directory
> into a container.
> 
> Steps to reproduce:
> 
>     1. sudo deboostrap bullseye /var/lib/machines/test
>     2. sudo systemd-nspawn -M test
>     3. Set root password, install dbus…
>     4. sudo systemd-nspawn -bM test
>     5. sudo machinectl bind test /path/to/some/dir --mkdir
>     
> The last command reliably fails with error message:
> 
>     Failed to bind mount: Failed to mount: No such file or directory
>     
> There is also an error message in systemd journal:
> 
>     авг 29 13:24:33 lenovo [18009]: Failed to mount
>     /run/host/incoming/5Ok22y (type n/a) on <path> (MS_MOVE ""): No such
>     file or directory
>     
> It doesn't depend on whether the target directory exists or not.
> 
> Bind mounts using --bind=… systemd-nspawn option work as expected.
> 

This seems to work fine with
249.3-4 from experimental. So marking as fixed for that version.

If you are interested in seeing this fixed in bullseye, it would be 
great if you can run git bisect to find the commit that fixed it.
If it's reasonable enough, we might consider backporting it.

Regards,
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/20210830/1b34d217/attachment.sig>