[systemd-devel] systemd-nspawn: starting multiple shells

[Nikolaus Rath]

On Jun 23 2018, aleivag <aleivag at gmail.com> wrote:
> short answer, yes, `machinectl login` is only suppported for systemd-init ,
> and `machinectl shell` `systemd-run` will try to talk to the container via
> dbus, so i dont think you are force to have systemd runing inside the
> container (i may be wrong) but you do need to have dbus (and its easy to
> just have systemd).  if you dont need it, you can always use nsenter to
> access a namespace on your machine

Still not working:

$ sudo systemd-nspawn -M $MACHINE --private-users=1379532800:65536
  --private-network -network-macvlan=eth0 --boot

# Other console
$ sudo machinectl list
MACHINE  CLASS     SERVICE        OS     VERSION ADDRESSES
iofabric container systemd-nspawn centos 7       192.168.0.26...

1 machines listed.

$ sudo machinectl shell root at iofabric
[sudo] password for nikratio: 
Failed to get shell PTY: Cannot set property StandardInputFileDescriptor, or unknown property.

$ machinectl --version
systemd 232
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN

Any idea?

Best,
-Nikolaus
-- 
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«