From 72553cb41411b2f7e6baf4d5e73f1c3b95da0a9a Mon Sep 17 00:00:00 2001 From: Lemon-miaow Date: Wed, 23 Sep 2026 19:35:13 +0800 Subject: [PATCH] =?UTF-8?q?docs(troubleshooting):=20the=20installer=20leav?= =?UTF-8?q?es=20docker=20stopped=20=E2=80=94=20start=20it=20before=20manua?= =?UTF-8?q?l=20pushes?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Both the §8e mirror recipe and the §13b re-mirror step run docker tag/push, and a fresh install (or re-run) ends with the daemon stopped. One line each so the runbook does not fail on 'Cannot connect to the Docker daemon'. --- docs/troubleshooting.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index c123698..42fa06b 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -417,7 +417,8 @@ build_mem_limit = "4Gi" Mirror the executor images into the registry once. On the node itself, push through the loopback hostPort the registry Deployment binds (docker treats -`127.0.0.1` as insecure by default): +`127.0.0.1` as insecure by default; the installer leaves the daemon stopped, so +`sudo systemctl start docker` first): ```sh docker pull gcr.io/kaniko-project/executor:v1.24.0 # any versions you pin @@ -779,7 +780,8 @@ If a pull does NOT come back: re-run the installer (it rewrites the file and restarts k3s only when the content changed). 4. Re-mirror a tag the registry does not have (hand-built images were never - pushed): `docker tag 127.0.0.1:5000/: && docker push + pushed): `sudo systemctl start docker` (the installer leaves the daemon + stopped), then `docker tag 127.0.0.1:5000/: && docker push 127.0.0.1:5000/:`. For an image that is in neither place, the old fallback still stands: re-run the