Default bridge network versus user‑defined bridge network for managing Docker IP address exhaustion
Goal: Decide whether to rely on Docker’s automatically created default bridge network or to create a user‑defined bridge network with a custom subnet in order to control the risk of IPv4 address exhaustion in environments with high container churn. Constraint: The default bridge uses a fixed 172.17.0.0/16 subnet (~65 000 addresses) and does not reclaim IPs f
docker