Bug#771675: systemd: machinectl: Failed to get container bus: Input/output error

Mario Lang mlang at tugraz.at
Mon Dec 1 14:24:31 GMT 2014


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 at host:/# mkdir /var/lib/container
root at 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 at 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 at debian-jessie:~# exit
root at 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 at fzidpc73:/# systemctl start systemd-nspawn at debian-jessie.service
root at fzidpc73:/# machinectl list
MACHINE                          CONTAINER SERVICE
debian-jessie                    container nspawn

1 machines listed.
root at 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.

-- Package-specific info:
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20141201/ae777d9c/attachment.ksh>
-------------- next part --------------

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  acl             2.2.52-2
ii  adduser         3.113+nmu3
ii  initscripts     2.88dsf-58
ii  libacl1         2.2.52-2
ii  libaudit1       1:2.4-1
ii  libblkid1       2.25.2-3
ii  libc6           2.19-13
ii  libcap2         1:2.24-6
ii  libcap2-bin     1:2.24-6
ii  libcryptsetup4  2:1.6.6-3
ii  libgcrypt20     1.6.2-4
ii  libkmod2        18-3
ii  liblzma5        5.1.1alpha+20120614-2+b2
ii  libpam0g        1.1.8-3.1
ii  libselinux1     2.3-2
ii  libsystemd0     215-7
ii  mount           2.25.2-3
ii  sysv-rc         2.88dsf-58
ii  udev            215-7
ii  util-linux      2.25.2-3

Versions of packages systemd recommends:
ii  dbus            1.8.12-1
ii  libpam-systemd  215-7

Versions of packages systemd suggests:
pn  systemd-ui  <none>

-- no debconf information

-- 
Regards,
      Mario Lang

Graz University of Technology        mailto:mlang at TUGraz.at
Department Computing               http://www.ZID.TUGraz.at/lang/
Phone: +43 (0) 316 / 873 - 6897
    /____________________________________________________________/
  /_Apparently a teacher has been arrested in the UK in possession_/
 /of a compass, protractor, and straight edge. It is claimed he is a/
/member of the Al Gebra movement, bearing weapons of math instruction/


More information about the Pkg-systemd-maintainers mailing list