Bug#858986: systemd-container: systemd-nspawn fails to spawn container from a read-only image

[Felix Wiedemann]

Package: systemd-container
Version: 232-19
Severity: normal

Dear Maintainer,

systemd-nspawn fails to spawn a container from an image which has a
read-only file system as root partition (SquashFS):

  $ systemd-nspawn -i foo.img
  Spawning container foo.img on /home/felix/foo.img.
  Press ^] three times within 1s to kill container.
  Failed to create directory /tmp/nspawn-root-jvD8mU/sys: Read-only file system

I filed the bug upstream [0] and it was fixed in systemd v233 [1].
Please consider backporting the patch to stretch.

[0]: https://github.com/systemd/systemd/issues/4711
[1]: https://github.com/systemd/systemd/commit/acbbf69b718260755a5dff60dd68ba239ac0d61b


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (600, 'testing'), (499, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-container depends on:
ii  dbus             1.10.16-1
ii  libacl1          2.2.52-3+b1
ii  libblkid1        2.29.1-1
ii  libbz2-1.0       1.0.6-8.1
ii  libc6            2.24-9
ii  libcurl3-gnutls  7.52.1-3
ii  libgcrypt20      1.7.6-1
ii  libip4tc0        1.6.0+snapshot20161117-5
ii  liblzma5         5.2.2-1.2+b1
ii  libseccomp2      2.3.1-2.1
ii  libselinux1      2.6-3+b1
ii  systemd          232-19
ii  zlib1g           1:1.2.8.dfsg-5

Versions of packages systemd-container recommends:
ii  btrfs-progs        4.7.3-1
ii  btrfs-tools        4.7.3-1
ii  libnss-mymachines  232-19

systemd-container suggests no packages.

-- no debconf information