Bug#778581: systemd install breaks chroot jail and compromises guest system
biebl at debian.org
Tue Feb 17 09:39:45 GMT 2015
Am 17.02.2015 um 01:13 schrieb Wolfgang Rosner:
> Package: systemd
> Version: 215-8
> Severity: normal
> Dear Maintainer,
> I'm trying to configure nfsroot installation for diskless clients.
> - <server$> debootstrap .... /path/to/client-root
> - <server$> chroot /path/to/client-root /bin/bash
> - CHR#> apt-get install <lots of stuff w/o problems>
> - CHR#> apt-get install systemd
> The last command leads to some error message (I can't remember)
> Then, after googling, I run something like dpkg -a (still in the chrooted shell)
> This made my server completely frozen.
> After forceful reboot, It seems that I got parts of systemd installed on the server, too, not only on the chrooted client-root.
> root at cruncher:/cluster/tftp/active/pxelinux.cfg# dpkg --list | grep systemd
> ii libpam-systemd:amd64 215-8 amd64 system and service manager - PAM module
> ii libsystemd-login0:amd64 44-11+deb7u4 amd64 systemd login utility library
> ii libsystemd0:amd64 215-8 amd64 systemd utility library
> ii systemd 215-8 amd64 system and service manager
> ii systemd-shim 9-1 amd64 shim for systemd
> root at cruncher:/cluster/tftp/active/pxelinux.cfg# grep systemd /var/log/apt/history.log
> ..... is EMPTY ....
> So I think systemd got installed accidentially by breaking the chroot.
What you describe sounds highly unlikely. Merely installing systemd in a
chroot will not "break the chroot".
To me it looks like you accidentally installed systemd on the host
system yourself, or it was already installed.
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...
Size: 834 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers