Your message dated Sat, 29 Apr 2017 21:30:31 +0200
with message-id <dcc63e8c-f6b9-c199-cca7-77d03be4c...@debian.org>
and subject line Re: Bug#858986: systemd-container: systemd-nspawn fails to
spawn container from a read-only image
has caused the Debian Bug report #858986,
regarding systemd-container: systemd-nspawn fails to spawn container from a
read-only image
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
858986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Version: 233-1
Am 29.04.2017 um 18:05 schrieb Felix Wiedemann:
> On 28.04.2017 22:16, Michael Biebl wrote:
>> On Wed, 29 Mar 2017 12:20:52 +0200 Felix Wiedemann
>>> 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.
>>
> I have a script attached to this mail which builds such a disk image.
> Also, I verfied that `systemd-nspawn -i $IMAGE` with such a disk image
> fails on stretch/v232 and on jessie-backports/v230. It works on jessie/v215.
Thanks for the script!
> I just tried to build systemd v232 with the commit applied on top, but
> it does not compile because it's missing the type 'MountSettingsMask'. I
> have not looked into that any further.
So, I looked into this a bit more today, and it seems a backport
requires other commits like [1]. I fear those changes are too invasive
for this point of the release cycle. I'm therefor closing this bug
report, as I don't plan to backport this change.
We will provide backports of newer upstream versions for stretch though,
so you will be able to get v233 (and later) via stretch-backports which
include this fix.
This doesn't quite address your request, but I guess this is the best we
can do unfortunately.
Regards,
Michael
[1]
https://github.com/systemd/systemd/commit/4f086aab52812472a24c9b8b627589880a38696e
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
