summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoshua Powers <josh.powers@canonical.com>2020-04-10 13:24:40 -0700
committerGitHub <noreply@github.com>2020-04-10 15:24:40 -0500
commite1a060487eeafc9c5944557f83c5a05e03b6852f (patch)
tree9206c05c807f64ed76023d1cbce9a0e7146cba0c
parente30599c103ff926e8cbf38f36d1ba071918fc386 (diff)
downloadvyos-cloud-init-e1a060487eeafc9c5944557f83c5a05e03b6852f.tar.gz
vyos-cloud-init-e1a060487eeafc9c5944557f83c5a05e03b6852f.zip
docs: Add steps to re-run cloud-id and cloud-init (#313)
-rw-r--r--doc/rtd/topics/faq.rst17
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/rtd/topics/faq.rst b/doc/rtd/topics/faq.rst
index 98c0cfaa..e3ad64a0 100644
--- a/doc/rtd/topics/faq.rst
+++ b/doc/rtd/topics/faq.rst
@@ -104,6 +104,23 @@ The force parameter allows the command to be run again since the instance has
already launched. The other options increase the verbosity of logging and
put the logs to STDERR.
+How can I re-run datasource detection and cloud-init?
+=====================================================
+
+If a user is developing a new datasource or working on debugging an issue it
+may be useful to re-run datasource detection and the initial setup of
+cloud-init.
+
+To do this, force ds-identify to re-run, clean up any logs, and re-run
+cloud-init:
+
+.. code-block:: shell-session
+
+ $ sudo DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force
+ $ sudo cloud-init clean --logs
+ $ sudo cloud-init init --local
+ $ sudo cloud-init init
+
How can I debug my user data?
=============================