nixos-manual: fix incomplete container doc

This commit is contained in:
Gaëtan André 2015-12-09 15:50:18 +01:00
parent a190cb7636
commit 099712f78d

View file

@ -22,8 +22,10 @@ containers.database =
</programlisting> </programlisting>
If you run <literal>nixos-rebuild switch</literal>, the container will If you run <literal>nixos-rebuild switch</literal>, the container will
be built and started. If the container was already running, it will be be built. If the container was already running, it will be
updated in place, without rebooting.</para> updated in place, without rebooting. Container can be configured to
start automatically by setting <literal>autoStart = true</literal>
in its configuration.</para>
<para>By default, declarative containers share the network namespace <para>By default, declarative containers share the network namespace
of the host, meaning that they can listen on (privileged) of the host, meaning that they can listen on (privileged)
@ -47,7 +49,9 @@ on container networking.)</para>
<para>To disable the container, just remove it from <para>To disable the container, just remove it from
<filename>configuration.nix</filename> and run <literal>nixos-rebuild <filename>configuration.nix</filename> and run <literal>nixos-rebuild
switch</literal>. Note that this will not delete the root directory of switch</literal>. Note that this will not delete the root directory of
the container in <literal>/var/lib/containers</literal>.</para> the container in <literal>/var/lib/containers</literal>. Containers can be
destroyed using the imperative method: <literal>nixos-container destroy
foo</literal>.</para>
<para>Declarative containers can be started and stopped using the <para>Declarative containers can be started and stopped using the
corresponding systemd service, e.g. <literal>systemctl start corresponding systemd service, e.g. <literal>systemctl start