From a1d4d82382bbd54764e04b4e05cc730b56f1179d Mon Sep 17 00:00:00 2001 From: Josh Bairstow Date: Wed, 3 Jun 2026 00:01:31 +1000 Subject: [PATCH] docs: note the desktop Docker daemon must be running/enabled for builds Stopped daemon surfaces as 'Cannot connect to the Docker daemon' at the build step (login works without it). Add the enable-at-boot recipe. Co-Authored-By: Claude Opus 4.8 (1M context) --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index d785006..a47837f 100644 --- a/README.md +++ b/README.md @@ -161,6 +161,16 @@ host using its Docker, not in a socket-less container). See [`runner/config.yml`](runner/config.yml) and [`runner/forgejo-runner.service`](runner/forgejo-runner.service). +The desktop's **Docker daemon must be running and enabled at boot** — the runner +builds against it. `docker login` works without the daemon but `docker build` +won't, so a stopped daemon shows up as *"Cannot connect to the Docker daemon"* +mid-pipeline. Ensure one daemon owns `/var/run/docker.sock`: +```sh +sudo snap stop --disable docker.dockerd # if a crashing snap docker is present +sudo systemctl enable --now docker.service # classic engine, on at boot +docker info | head # verify as your user, no sudo +``` + ### 6. Wire the jb-website repo In the `jb-website` repo settings on Forgejo (`Settings → Actions`):