joshbairstow/jb-infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: note the desktop Docker daemon must be running/enabled for builds

Browse source 
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) <noreply@anthropic.com>
This commit is contained in:
Josh Bairstow 2026-06-03 00:01:31 +10:00
parent 5bb124acfd
commit a1d4d82382
1 changed files with 10 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

10
README.md
View file

@ -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`):