Bug#876103: systemd-nspawn: --read-only is broken

2017-12-03 Thread Lauri Tirkkonen
Hi, On Sun, Dec 03 2017 13:47:29 +0100, Michael Biebl wrote: > > There is an upstream fix for this in > > https://github.com/systemd/systemd/pull/4693 -- > > acbbf69b718260755a5dff60dd68ba239ac0d61b is the commit that actually > > fixes read-only containers, but it requires two other commits to

Bug#876103: systemd-nspawn: --read-only is broken

2017-12-03 Thread Michael Biebl
Am 18.09.2017 um 15:43 schrieb Lauri Tirkkonen: > Package: systemd-container > Version: 232-25+deb9u1 > Severity: normal > > Dear Maintainer, > > on stretch, 'systemd-nspawn --read-only' fails to start the container > entirely. Trivial test case: > > # machinectl pull-tar >

Bug#876103: systemd-nspawn: --read-only is broken

2017-09-18 Thread Lauri Tirkkonen
Package: systemd-container Version: 232-25+deb9u1 Severity: normal Dear Maintainer, on stretch, 'systemd-nspawn --read-only' fails to start the container entirely. Trivial test case: # machinectl pull-tar