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

docs: note Fedora docker0 ZONE_CONFLICT fix for the runner host

Browse source 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Josh Bairstow 2026-06-03 00:08:11 +10:00
parent a1d4d82382
commit 75bfd3a516
1 changed files with 8 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -170,6 +170,14 @@ sudo snap stop --disable docker.dockerd # if a crashing snap docker is pres
sudo systemctl enable --now docker.service # classic engine, on at boot sudo systemctl enable --now docker.service # classic engine, on at boot
docker info | head # verify as your user, no sudo docker info | head # verify as your user, no sudo
``` ```
Fedora gotcha: if `dockerd` then fails with
`ZONE_CONFLICT: 'docker0' already bound to 'FedoraWorkstation'` (a stale binding,
often left by a prior snap-docker), free the interface and retry:
```sh
sudo firewall-cmd --permanent --zone=FedoraWorkstation --remove-interface=docker0
sudo firewall-cmd --reload && sudo ip link delete docker0 2>/dev/null
sudo systemctl reset-failed docker.service && sudo systemctl start docker.service
```
### 6. Wire the jb-website repo ### 6. Wire the jb-website repo
In the `jb-website` repo settings on Forgejo (`Settings → Actions`): In the `jb-website` repo settings on Forgejo (`Settings → Actions`):