Am 01.12.2014 um 15:24 schrieb Mario Lang: > Package: systemd > Version: 215-7 > Severity: minor > > Trying to access a container with "machinectl login" fails. > But booting the container manually gives a login prompt. > > root@host:/# mkdir /var/lib/container > root@host:/# debootstrap jessie /var/lib/container/debian-jessie > I: Retrieving Release I: Retrieving Release.gpg > I: Checking Release signature > ... > I: Base system installed successfully. > root@host:/# systemd-nspawn -D /var/lib/container/debian-jessie > Spawning container debian-jessie on /var/lib/container/debian-jessie. > Press ^] three times within 1s to kill container. > /etc/localtime is not a symlink, not updating container timezone. > root@debian-jessie:~# exit > root@fzidpc73:/# systemd-nspawn -bD /var/lib/container/debian-jessie > ... > Debian GNU/Linux jessie/sid fzidpc73 console > > fzidpc73 login: > > OK, so the container boots with systemd-nspawn, but: > > root@fzidpc73:/# systemctl start systemd-nspawn@debian-jessie.service > root@fzidpc73:/# machinectl list > MACHINE CONTAINER SERVICE > debian-jessie container nspawn > > 1 machines listed. > root@fzidpc73:~# machinectl login debian-jessie > Failed to get container bus: Input/output error > > > I am confused, possibly because I don't fully get all the technology > involed yet. machinectl *sees* the running machine, but it fails to > connect to it, with a rather generic error message.
Actually, the message is not that generic. It fails to connect to the container bus. After installing the "dbus" package inside the container (and rebooting it), you should be able to use "machinectl login" -- 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
