nixos: nixos/doc/manual/administration/containers.xml to CommonMark
This commit is contained in:
parent
8882ec6ff9
commit
5aaeddee5f
28
nixos/doc/manual/administration/containers.chapter.md
Normal file
28
nixos/doc/manual/administration/containers.chapter.md
Normal file
|
@ -0,0 +1,28 @@
|
||||||
|
# Container Management {#ch-containers}
|
||||||
|
|
||||||
|
NixOS allows you to easily run other NixOS instances as *containers*.
|
||||||
|
Containers are a light-weight approach to virtualisation that runs
|
||||||
|
software in the container at the same speed as in the host system. NixOS
|
||||||
|
containers share the Nix store of the host, making container creation
|
||||||
|
very efficient.
|
||||||
|
|
||||||
|
::: {.warning}
|
||||||
|
Currently, NixOS containers are not perfectly isolated from the host
|
||||||
|
system. This means that a user with root access to the container can do
|
||||||
|
things that affect the host. So you should not give container root
|
||||||
|
access to untrusted users.
|
||||||
|
:::
|
||||||
|
|
||||||
|
NixOS containers can be created in two ways: imperatively, using the
|
||||||
|
command `nixos-container`, and declaratively, by specifying them in your
|
||||||
|
`configuration.nix`. The declarative approach implies that containers
|
||||||
|
get upgraded along with your host system when you run `nixos-rebuild`,
|
||||||
|
which is often not what you want. By contrast, in the imperative
|
||||||
|
approach, containers are configured and updated independently from the
|
||||||
|
host system.
|
||||||
|
|
||||||
|
```{=docbook}
|
||||||
|
<xi:include href="imperative-containers.section.xml" />
|
||||||
|
<xi:include href="declarative-containers.section.xml" />
|
||||||
|
<xi:include href="container-networking.section.xml" />
|
||||||
|
```
|
|
@ -1,34 +0,0 @@
|
||||||
<chapter xmlns="http://docbook.org/ns/docbook"
|
|
||||||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
|
||||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
||||||
version="5.0"
|
|
||||||
xml:id="ch-containers">
|
|
||||||
<title>Container Management</title>
|
|
||||||
<para>
|
|
||||||
NixOS allows you to easily run other NixOS instances as
|
|
||||||
<emphasis>containers</emphasis>. Containers are a light-weight approach to
|
|
||||||
virtualisation that runs software in the container at the same speed as in
|
|
||||||
the host system. NixOS containers share the Nix store of the host, making
|
|
||||||
container creation very efficient.
|
|
||||||
</para>
|
|
||||||
<warning>
|
|
||||||
<para>
|
|
||||||
Currently, NixOS containers are not perfectly isolated from the host system.
|
|
||||||
This means that a user with root access to the container can do things that
|
|
||||||
affect the host. So you should not give container root access to untrusted
|
|
||||||
users.
|
|
||||||
</para>
|
|
||||||
</warning>
|
|
||||||
<para>
|
|
||||||
NixOS containers can be created in two ways: imperatively, using the command
|
|
||||||
<command>nixos-container</command>, and declaratively, by specifying them in
|
|
||||||
your <filename>configuration.nix</filename>. The declarative approach implies
|
|
||||||
that containers get upgraded along with your host system when you run
|
|
||||||
<command>nixos-rebuild</command>, which is often not what you want. By
|
|
||||||
contrast, in the imperative approach, containers are configured and updated
|
|
||||||
independently from the host system.
|
|
||||||
</para>
|
|
||||||
<xi:include href="../from_md/administration/imperative-containers.section.xml" />
|
|
||||||
<xi:include href="../from_md/administration/declarative-containers.section.xml" />
|
|
||||||
<xi:include href="../from_md/administration/container-networking.section.xml" />
|
|
||||||
</chapter>
|
|
|
@ -16,6 +16,6 @@
|
||||||
<xi:include href="../from_md/administration/control-groups.chapter.xml" />
|
<xi:include href="../from_md/administration/control-groups.chapter.xml" />
|
||||||
<xi:include href="../from_md/administration/logging.chapter.xml" />
|
<xi:include href="../from_md/administration/logging.chapter.xml" />
|
||||||
<xi:include href="../from_md/administration/cleaning-store.chapter.xml" />
|
<xi:include href="../from_md/administration/cleaning-store.chapter.xml" />
|
||||||
<xi:include href="containers.xml" />
|
<xi:include href="../from_md/administration/containers.chapter.xml" />
|
||||||
<xi:include href="troubleshooting.xml" />
|
<xi:include href="troubleshooting.xml" />
|
||||||
</part>
|
</part>
|
||||||
|
|
|
@ -0,0 +1,31 @@
|
||||||
|
<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude" xml:id="ch-containers">
|
||||||
|
<title>Container Management</title>
|
||||||
|
<para>
|
||||||
|
NixOS allows you to easily run other NixOS instances as
|
||||||
|
<emphasis>containers</emphasis>. Containers are a light-weight
|
||||||
|
approach to virtualisation that runs software in the container at
|
||||||
|
the same speed as in the host system. NixOS containers share the Nix
|
||||||
|
store of the host, making container creation very efficient.
|
||||||
|
</para>
|
||||||
|
<warning>
|
||||||
|
<para>
|
||||||
|
Currently, NixOS containers are not perfectly isolated from the
|
||||||
|
host system. This means that a user with root access to the
|
||||||
|
container can do things that affect the host. So you should not
|
||||||
|
give container root access to untrusted users.
|
||||||
|
</para>
|
||||||
|
</warning>
|
||||||
|
<para>
|
||||||
|
NixOS containers can be created in two ways: imperatively, using the
|
||||||
|
command <literal>nixos-container</literal>, and declaratively, by
|
||||||
|
specifying them in your <literal>configuration.nix</literal>. The
|
||||||
|
declarative approach implies that containers get upgraded along with
|
||||||
|
your host system when you run <literal>nixos-rebuild</literal>,
|
||||||
|
which is often not what you want. By contrast, in the imperative
|
||||||
|
approach, containers are configured and updated independently from
|
||||||
|
the host system.
|
||||||
|
</para>
|
||||||
|
<xi:include href="imperative-containers.section.xml" />
|
||||||
|
<xi:include href="declarative-containers.section.xml" />
|
||||||
|
<xi:include href="container-networking.section.xml" />
|
||||||
|
</chapter>
|
Loading…
Reference in a new issue