From e365427d1b83c36b86e352c8f402e07b5eb2535f Mon Sep 17 00:00:00 2001 From: YueGuobin Date: Sat, 5 Sep 2026 00:55:12 +0800 Subject: [PATCH] docs: spell out IOL startup-config knob consumption in the node environment --- docs/features/iol-runner-docker.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/features/iol-runner-docker.md b/docs/features/iol-runner-docker.md index 231d6732d..c5b9fa56d 100644 --- a/docs/features/iol-runner-docker.md +++ b/docs/features/iol-runner-docker.md @@ -136,7 +136,12 @@ from it boots with that configuration as its personal starting point. * **Creation materializes it once**: the controller reads the file and sends its content with the node; afterwards the knob is consumed and the template file is never referenced again — editing it does not affect - existing nodes. + existing nodes. The knob also disappears from the node's `environment` + (`GNS3_IOL_RUNNER=1` remains — it re-selects the node class on every + recreation), so a node whose environment shows only `GNS3_IOL_RUNNER=1` + is the normal sign that the file was found and its content delivered; + when the file is missing the knob stays in the environment (with a + server-side warning) and the lookup is retried at the next creation. * **NVRAM is the source of truth at boot** (verified on the runner): the content is built into the node's `tmp/run/nvram_` — IOL and IOU share the nvram container format, so the server-side `nvram_import`