From 099712f78dad5bbd2bc7279cf0cfe67f2a25803b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ga=C3=ABtan=20Andr=C3=A9?= Date: Wed, 9 Dec 2015 15:50:18 +0100 Subject: [PATCH] nixos-manual: fix incomplete container doc --- .../manual/administration/declarative-containers.xml | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/nixos/doc/manual/administration/declarative-containers.xml b/nixos/doc/manual/administration/declarative-containers.xml index 228c45b0c1f..253be80b9c4 100644 --- a/nixos/doc/manual/administration/declarative-containers.xml +++ b/nixos/doc/manual/administration/declarative-containers.xml @@ -22,8 +22,10 @@ containers.database = If you run nixos-rebuild switch, the container will -be built and started. If the container was already running, it will be -updated in place, without rebooting. +be built. If the container was already running, it will be +updated in place, without rebooting. Container can be configured to +start automatically by setting autoStart = true +in its configuration. By default, declarative containers share the network namespace of the host, meaning that they can listen on (privileged) @@ -41,13 +43,15 @@ containers.database = This gives the container a private virtual Ethernet interface with IP address 192.168.100.11, which is hooked up to a virtual Ethernet interface on the host with IP address -192.168.100.10. (See the next section for details +192.168.100.10. (See the next section for details on container networking.) To disable the container, just remove it from configuration.nix and run nixos-rebuild switch. Note that this will not delete the root directory of -the container in /var/lib/containers. +the container in /var/lib/containers. Containers can be +destroyed using the imperative method: nixos-container destroy + foo. Declarative containers can be started and stopped using the corresponding systemd service, e.g. systemctl start