systemd-nspawn: starting multiple shells

[nikolaus@xxxxxxxx (Nikolaus Rath)]

Hi,

On Sat, 23 Jun 2018, at 15:31, Vito Caputo wrote:
> On Sat, Jun 23, 2018 at 03:09:04PM +0100, Nikolaus Rath wrote:
> > How would I go about starting an additional shell in an existing
> > container? I am starting the container with:
> >
> > $ systemd-nspawn -M foo --as-pid2 --register=no
> >
> > "foo" is a raw image retrieved with machinectl. If I simply execute the
> > above command again, I am getting a "Disk image
> > /var/lib/machines/foo.raw is currently busy." error.
> >
> > I've looked into the systemd-nspawn manpage, but couldn't find anything
> > appropriate.
> >
> > What am I missing?
> >
> Take a look at the machinectl man page, the "shell" and "login"
> subcommands in particular.

`man systemd-nspawn` says that when not running an init system in the container,
I should specify `--register=no`. But without that, `machinectl` doesn't do
anything.  Does this mean I need to run an init system to support multiple
shells?

Best,
-Nikolaus

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

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