$ cat dealing-with-concurrent-bridge-network-creates-host-port-races-in-docker.md
Dealing with concurrent bridge-network creates & host-port races in Docker
The author describes moving CI from GitHub-hosted runners to self-hosted arm64 machines, where each test shard starts its own MySQL, Redis, and ClickHouse containers under rootless Docker. The article covers the concurrency problems this setup creates, specifically races when creating bridge networks and binding host ports.
ma.ttias.be22 Jun 2026 · 1 min read · summary
Read on ma.ttias.be ↗I’ve been moving our CI off GitHub-hosted runners onto our own arm64 hardware. The plan was straightforward: a pool of ephemeral runners on a dedicated CI box, and each test shard spins up its own MySQL, Redis, and ClickHouse as service containers, all under rootless Docker.
source
This is a summary of an article first published by ma.ttias.be. The full piece is on their site.