David Thompson <[email protected]> skribis:
> From: David Thompson <[email protected]>
>
> * guix/scripts/system.scm (show-help): Display 'container' action.
> (system-derivation-for-action, guix-system): Add 'container' case.
> (perform-action): Skip GRUB config generation when building a container.
> * doc/guix.texi (Invoking guix system): Document it.
[...]
> +@item container
> +Return a script to run the operating system declared in @var{file}
> +within a container. Currently, the script must be run as root in order
@dfn{container} + @cindex container
What about adding something like this after the first sentence:
Containers are a set of lightweight isolation mechanisms provided by
the kernel Linux-libre. Containers are substantially less
resource-demanding than full virtual machines since the kernel, shared
objects, and other resources can be shared with the host system; this
also means they provide thinner isolation.
> +to support more than a single user and group.
> +
> +The container shares its store with the host system.
> +
> +Additional file systems can be shared between the host and the container
> +using the @code{--share} and @code{--expose} command-line options: the
> +former specifies a directory to be shared with write access, while the
> +latter provides read-only access to the shared directory.
> +
> +The example below creates a container in which the user's home directory
> +is accessible read-only, and where the @file{/exchange} directory is a
> +read-write mapping of the host's @file{$HOME/tmp}:
Instead of these two paragraphs (which duplicate those above), what
about:
As with the @code{vm} action (@pxref{the name of an anchor added above
in the right place}), additional file systems to be shared between the
host and container can be specified using the @option{--share} and
@option{--expose} options:
OK with changes along these lines!
Thanks,
Ludo’.
