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

2024-07-23 Thread Luca Boccassi
Control: tags -1 -moreinfo Control: close -1 The logs are showing what the issues are: /var/lib/machines/debian-sid.nspawn:4: Unknown key 'PrivateUsersChown' in section [Exec], ignoring. Ignoring TemporaryFileSystem=, Bind= and BindReadOnly= settings, file /var/lib/machines/debian-sid.nspawn is

Bug#1076616:

2024-07-22 Thread Josh Santos
I've just had a second to get to my workstation and check the logs as you've requested. Please note that I'll be in transit to Busan soon for DebCamp so my responses might be a bit delayed as I'm working on closing out many tasks prior to that. I think I might see what the issue is (maybe the docs

Bug#1076616:

2024-07-22 Thread Josh Santos
Using the config file as in the Debian packager documentation linked doesn't work for either myself or an existing packager (who's IRC handle was mentioned in original report) Does the bind mount work for you when following that documentation and using the config file option in the .nspawn file?

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

2024-07-19 Thread Luca Boccassi
Control: tags -1 unreproducible moreinfo On Sat, 20 Jul 2024 01:21:45 +0700 Josh Santos wrote: > Package: systemd-container > Version: 252.26-1~deb12u2 > Severity: normal > X-Debbugs-Cc: j...@omnidapps.com > > Dear Maintainer, >    * What led up to the situation? >    Running a container using n

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

2024-07-19 Thread Josh Santos
Package: systemd-container Version: 252.26-1~deb12u2 Severity: normal X-Debbugs-Cc: j...@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 *