Open jaspertandy opened 5 months ago
@jaspertandy Thanks for reporting.
We recently discussed that internally and an Engine user also opened an issue to change the list of 'default address pools' (see https://github.com/moby/moby/pull/47737) -- this would make more subnets available.
We want to merge another change first, and then we'll change that default value. This should be fixed in a few versions.
As a workaround, you can put this in your daemon.json
(Settings > Docker Engine):
{
"default-address-pools": [
{"base": "172.16.0.0/16", "size": 24},
{"base": "192.168.0.0/16", "size": 24}
]
}
@akerouanton thanks so much, and thank you for the temporary workaround. That's especially appreciated, as I mentioned I'm stuck on an older version so wouldn't be able to upgrade anyway. Really appreciate your quick reply on this.
Description
I've always had this issue with Docker for Mac where every now and again I need to clear out all my networks and start over, but it's happening increasingly often now, and has just happened to me today where I run a new
docker compose up
because I'm out of networks.My networks:
I've solved this previously with a
docker system prune
but I would prefer to solve this by setting my Resources > Network Docker subnet to something like172.16.20.0/22
. However, this field only seems to allow a/24
CIDR. What's going on here? This limitation is super annoying when you work in an agency with lots of projects.Reproduce
Expected behavior
I should be able to create many more networks.
docker version
docker info
Diagnostics ID
0FCC5372-02A5-4C31-9906-384A4F1AEEE5/20240501133406
Additional Info
I know I'm on an older version of Docker for Mac but I am affected by this issue and can't upgrade until it's solved.