From 74df71bc8b446dd803aed3990a1148f258772f65 Mon Sep 17 00:00:00 2001 From: Tuomas Tynkkynen Date: Sun, 30 Sep 2018 03:18:58 +0300 Subject: [PATCH] Revert "doc: Update section about imperative containers" This reverts commit f309440ee3b6830fd886f824be81b0fecfba52fc. Breaks manual build: https://nix-cache.s3.amazonaws.com/log/wnjcy6n5f871bpyy9nd06smiz1ggv99c-nixos-manual-combined.drv --- .../administration/imperative-containers.xml | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/nixos/doc/manual/administration/imperative-containers.xml b/nixos/doc/manual/administration/imperative-containers.xml index cfd0e5c172b134..9bb62bc2ece9e8 100644 --- a/nixos/doc/manual/administration/imperative-containers.xml +++ b/nixos/doc/manual/administration/imperative-containers.xml @@ -73,7 +73,8 @@ Linux foo 3.4.82 #1-NixOS SMP Thu Mar 20 14:44:05 UTC 2014 x86_64 GNU/Linux - To change the configuration of the container, you can edit + There are several ways to change the configuration of the container. First, + on the host, you can edit /var/lib/container/name/etc/nixos/configuration.nix, and run @@ -86,16 +87,7 @@ Linux foo 3.4.82 #1-NixOS SMP Thu Mar 20 14:44:05 UTC 2014 x86_64 GNU/Linux = true; = "foo@example.org"; = [ 80 ]; - ' - - - Note that in previous versions of NixOS (17.09 and earlier) one could - also use all nix-related commands (like nixos-rebuild switch) - from inside the container. However, since the release of Nix 2.0 this - is not supported anymore. Supporting Nix commands inside the - container might be possible again in future versions. See - the github issue for tracking progress on this issue. - +' # curl http://$(nixos-container show-ip foo)/ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">… @@ -104,6 +96,14 @@ Linux foo 3.4.82 #1-NixOS SMP Thu Mar 20 14:44:05 UTC 2014 x86_64 GNU/Linux /etc/nixos/configuration.nix. + + Alternatively, you can change the configuration from within the container + itself by running nixos-rebuild switch inside the + container. Note that the container by default does not have a copy of the + NixOS channel, so you should run nix-channel --update + first. + + Containers can be stopped and started using nixos-container stop and nixos-container start, respectively, or