[systemd-devel] systemd-nspawn: where is my container root?

[Ryan Gonzalez]

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 <Nikolaus at rath.org> wrote:

> 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 the host?
>
> I have downloaded a .qcow2 image with machinectl fetch-raw. Since the
> manpage encouraged it, I also put /var/lib/machines on a btrfs
> filesystem. However, even when I am logged into the container, the only
> entries in there are two .raw files. "mount" also does not show me any
> new mountpoints.
>
> Where and how is the root filesystem mounted, and how can I access it
> *from the host*? I would have expected to see a new mountpoint, or a new
> btrfs subvolume..
>
> 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