Hi: to get a shell on your running container , you need to get it's name (execute `machinectl` to get a list of containers) and then if you just want a shell you can run `systemd-run --machine=<name> --pty /bin/bash` or `machinectl shell <name> /bin/bash` and if you want a real login promp machinectl login <name> is your best bet hope it helps Alvaro Leiva Geisse On Sat, Jun 23, 2018 at 7:13 AM Nikolaus Rath <Nikolaus at rath.org> 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? > > > Thanks! > -Nikolaus > > -- > GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F > > »Time flies like an arrow, fruit flies like a Banana.« > _______________________________________________ > systemd-devel mailing list > systemd-devel at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20180623/445fa10e/attachment.html>