Environment TestandClaude Sonnet 4.6
83262816a3
- Move emojis after headline text (CONTRIBUTING.md, actions/, design/, tools/, tests/) - Replace em dashes with colons, semicolons, or complete sentences throughout - Add missing emojis to all headlines in exceptions.md, principles.md, services.md, shell.md, setup.md, pull-request.md, commit.md, act.md, docker.md, pr/README.md - Update H1 titles to reflect renamed directories (actions/, design/) - Fix broken relative links in workflow.md after directory moves - Fix full-path link texts in services.md (style.css.md, javascript.js.md) - Fix broken principles.md link to lint.md after testing/ → actions/testing/ move Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2.1 KiB
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.
The local development compose stack SHOULD inherit the host Docker MTU automatically from /etc/docker/daemon.json. If auto-detection is unavailable or wrong, you MAY override it explicitly with INFINITO_OUTER_NETWORK_MTU.
ip link show docker0
ip link show eth0
Fix via /etc/docker/daemon.json:
{"mtu": 1450}
Then restart Docker:
sudo systemctl restart docker
For a one-off local override, export the variable before starting the stack:
export INFINITO_OUTER_NETWORK_MTU=1400
make up
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/
The recommended way to disable IPv6 for local development is via Make:
make disable-ipv6
This also restarts docker.service and then calls make refresh, so the running Infinito development stack is recreated when one is active and the new setting reaches fresh container network namespaces.
To restore the original IPv6 settings afterwards:
make restore-ipv6
This restore path also restarts docker.service and then calls make refresh, so the running Infinito development stack is recreated when one is active and the restored setting reaches fresh container network namespaces.
You can also refresh the running local stack directly after host-level changes:
make refresh
Alternatively, disable IPv6 only 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.