Package: systemd-container Version: 252.26-1~deb12u2 Severity: normal X-Debbugs-Cc: [email protected]
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@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. -- System Information: Debian Release: 12.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-23-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd-container depends on: ii dbus [default-dbus-system-bus] 1.14.10-1~deb12u1 ii libacl1 2.3.1-3 ii libbz2-1.0 1.0.8-5+b1 ii libc6 2.36-9+deb12u7 ii libcurl4 7.88.1-10+deb12u6 ii liblzma5 5.4.1-0.2 ii libseccomp2 2.5.4-1+deb12u1 ii libselinux1 3.4-1+b6 ii libssl3 3.0.13-1~deb12u1 ii libsystemd-shared 252.26-1~deb12u2 ii systemd 252.26-1~deb12u2 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages systemd-container recommends: ii libnss-mymachines 252.26-1~deb12u2 systemd-container suggests no packages. -- no debconf information
