It's probably a private mountpoint, meaning that no one outside of
systemd-nspawn and it's children can see it. If you need to access the
data, you can use machinectl:
https://www.freedesktop.org/software/systemd/man/machinectl.html
On June 23, 2018 8:49:01 AM Nikolaus Rath wrote:
Hi,
I h
hi:
so for finding the pid the solution its (big surprise :D ) using systemd,
instead of just executing you systemd-nspawn in bash you start it as a
systemd-unit (you can even do this as ephemeral unit with `sytemd-run
--unit myspawn.service systemd-nspawn bla...`)
then to get the ip of the n
On Jun 23 2018, Nikolaus Rath wrote:
> On Jun 23 2018, aleivag 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 t
On Jun 23 2018, aleivag 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
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
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
> >
>
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
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= --pty
/bin/bash` or `machinectl shell /bin/bash`
and if you want a real login promp
machinectl login
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/ma
Hi,
I have just started using machinectl and systemd-nspawn and like it a
lot. However, there is one thing that I could not figure out from the
documentation and not knowing it makes me feel uncomfortable: where
exactly is the root filesystem for the container mounted, and how can I
access it from
Hello,
When running systemd-nspawn with --private-network, I am getting mount
errors:
# systemd-nspawn -M iofabric --as-pid2 --private-users=1379532800:65536
--register=no --private-network
Spawning container iofabric on /var/lib/machines/iofabric.raw.
Press ^] three times within 1s to kill cont
11 matches
Mail list logo
