Bug#1076616: systemd-container: Bind mounts not working

[Luca Boccassi]

Control: tags -1 unreproducible moreinfo

On Sat, 20 Jul 2024 01:21:45 +0700 Josh Santos <josh at omnidapps.com>
wrote:
> Package: systemd-container
> Version: 252.26-1~deb12u2
> Severity: normal
> X-Debbugs-Cc: josh at omnidapps.com
> 
> Dear Maintainer,
>    * What led up to the situation?
>    Running a container using nspawn with a bind mount such as is
described here: https://wiki.debian.org/Packaging/Pre-Requisites/nspawn
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
>    systemctl start systemd-nspawn at debian-sid
> 
>    * What was the outcome of this action?
>    Launches fine, but bind mount is non-existent.
> 
>    * What outcome did you expect instead?
>    Expected the bind mount to be present
> 
>    * Additional context: pirate_praveen on DebConf IRC confirms this
happens on their system which is running Debian Sid.

This is working just fine here on stable:

$ mkdir -p /tmp/foo/bar
$ sudo systemd-nspawn --quiet --bind /tmp/foo --directory ~/images/noble/ ls -l /tmp/foo
total 0
drwxr-xr-x 2 1000 1000 40 Jul 19 23:09 bar

so you need to attach the exact command you are using, run it with
SYSTEMD_LOG_LEVEL=debug and also attach the logs

-- 
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20240719/65c8e604/attachment.sig>