On Sat, Jun 23, 2018 at 03:09:04PM +0100, Nikolaus Rath wrote: > Hello, > > 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. Regards, Vito Caputo _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
