0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-08 11:46:35 +00:00

Files

T

kevinveenbirkenbachandClaude Sonnet 4.6 79ca7137da docs: restructure debugging and CI flow documentation

- Rename continuous_integration.md to ci.md
- Move debugging.md into debugging/ci.md and apply documentation standards
- Add debugging/network.md with Docker pull error guidance (MTU, IPv6, connectivity)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-03-31 19:21:38 +02:00

1007 B

Raw Blame History

Network 🌐

Docker Pull Errors 🐳

Images cannot be pulled separately, as they run inside a container.

If a docker pull or general image pull fails, it may be caused by an MTU, network, or IPv6 issue on the host PC. Check and fix accordingly:

MTU 📦

Docker defaults to MTU 1500. If the host network uses a smaller MTU (e.g. due to VPN), packets may be dropped or fragmented.

ip link show docker0
ip link show eth0

Fix via /etc/docker/daemon.json:

{"mtu": 1450}

Then restart Docker:

sudo systemctl restart docker

IPv6 🔢

If IPv6 is active but misconfigured, Docker may attempt to pull over IPv6 and fail.

ip -6 addr show
curl -6 https://registry-1.docker.io/v2/

Disable IPv6 in Docker via /etc/docker/daemon.json:

{"ipv6": false}

General Connectivity 🔌

ping -c 3 registry-1.docker.io
curl -v https://registry-1.docker.io/v2/

Check firewall rules, proxy settings, and DNS configuration.

1007 B Raw Blame History