Bug#755160: Segfault when starting new system instance in a systemd-nspawn environment

[Michael Biebl]

Hi Christoph

On Sat, 19 Jul 2014 00:03:23 +0200 Michael Biebl <biebl at debian.org> wrote:
> Am 18.07.2014 13:56, schrieb Christoph Berg:
> > Package: systemd
> > Version: 204-14
> > Severity: normal
> > 
> > Hi,
> > 
> > my host system is jessie. In my sid-amd64 chroot which I entered using
> > systemd-nspawn, I tried to start a new systemd --system instance:
> > 
> > $ sudo systemd-nspawn -D /srv/src/chroot/sid-amd64
> > Spawning namespace container on /srv/src/chroot/sid-amd64 (console is /dev/pts/4).
> > Init process in the container running as PID 27787.
> > /etc/localtime is not a symlink, not updating container timezone.
> > 
> > (sid-amd64)root at sid-amd64:~# apt-get install systemd
> > [...]
> > Setting up libsystemd-daemon0:amd64 (208-6) ...
> > Setting up libsystemd-journal0:amd64 (208-6) ...
> > Setting up libsystemd-login0:amd64 (208-6) ...
> > Setting up acl (2.2.52-1) ...
> > Setting up libcap2-bin (1:2.22-2) ...
> > Setting up libdevmapper1.02.1:amd64 (2:1.02.85-2) ...
> > Setting up libcryptsetup4:amd64 (2:1.6.4-4) ...
> > Setting up systemd (208-6) ...
> 
> I wonder if this is related to the version mismatch, i.e. v204 vs v208.

I tried the other way around: host systemd is sid (v228), chroot is
jessie (v215).
I didn't experience any segfaults. Could you try if you can reproduce
the issue with current versions for systemd?

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: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160128/be52dc96/attachment.sig>