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

[Michael Biebl]

Hi Felix

On Wed, 29 Mar 2017 12:20:52 +0200 Felix Wiedemann
<1wiedema at informatik.uni-hamburg.de> wrote:
> 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

Have you confirmed that applying this commit on top of v232 fixes the
issue you have? Otherwise, can you give me instructions how to create
such a read-only image or provide one for me, so I can test it myself.

Regards,
Michael




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170428/9a5c2eea/attachment.sig>