summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDan Rostovtsev <dan@rostovtsev.org>2026-03-15 19:10:43 -0400
committerDan Rostovtsev <dan@rostovtsev.org>2026-03-15 19:10:43 -0400
commit9f434b57b7fc477894e52c47a6cf565da3b43b2d (patch)
tree9ce55a5fdd5f1d2c4069d8ca56da0985d6448c3c
parent9a2d526cd356b216098964e4939198532b1a2bdf (diff)
Added instructions for deploying machine configurations.linode-image-docs
-rw-r--r--doc/examples/guix-on-linode.scm (renamed from doc/examples/cloud-guix.scm)3
-rw-r--r--doc/guix-cookbook.texi18
2 files changed, 16 insertions, 5 deletions
diff --git a/doc/examples/cloud-guix.scm b/doc/examples/guix-on-linode.scm
index 3d4bde024fd..56acf53b640 100644
--- a/doc/examples/cloud-guix.scm
+++ b/doc/examples/guix-on-linode.scm
@@ -1,6 +1,7 @@
;; Most cloud service providers use qemu / cloud-init to run images inside
;; inside of a virtual machine. This example was written for the "linode"
-;; tutorial originally, but it should apply to other cloud services as well.
+;; tutorial originally, but it should apply similarly other cloud services
+;; as well.
(use-modules (gnu)
(guix modules))
diff --git a/doc/guix-cookbook.texi b/doc/guix-cookbook.texi
index 4256957d3cf..4668de11fc4 100644
--- a/doc/guix-cookbook.texi
+++ b/doc/guix-cookbook.texi
@@ -3011,18 +3011,18 @@ system init} to initialize the guix installation. Replace the authorized
keys with the path to your keys.
@lisp
-@include examples/cloud-guix.scm
+@include examples/guix-on-linode.scm
@end lisp
Copy this to your linode in whatever directory you choose. In this
-example, we choose to call the file @file{cloud-guix.scm} and save it
-to @file{/tmp/cloud-guix.scm}.
+example, we choose to call the file @file{guix-on-linode.scm} and save it
+to @file{/tmp/guix-on-linode.scm}.
Now we are ready to install a guix system realizing this config to
@file{/mnt/guix}.
@example
-guix system init /tmp/cloud-guix.scm /mnt/guix
+guix system init /tmp/guix-on-linode.scm /mnt/guix
@end example
@subsection Configure Linode to Boot from Guix Image
@@ -3093,6 +3093,16 @@ Note that your coordinator machine will have to generate a public key,
which will be stored in @file{/etc/guix}. Copy that over to the target
machine and authorize it before running the deployment.
+If at the last step you are having issues with the authorization after running
+
+@example
+# guix archive --authorize < coordinator-key.pub
+@end example
+
+Then you likely have to add the key to the authorized keys in the herd
+service definition. For details, see
+@pxref{Getting Substitutes from Other Servers,,, guix, GNU Guix}.
+
@subsection Notes
Here are some other approaches that may work as well.