-
-
Save sunsided/7840e89ff4e11b64a2d7503fafa0290c to your computer and use it in GitHub Desktop.
{ | |
"bip": "172.39.1.5/24", | |
"fixed-cidr": "172.39.1.0/25", | |
"runtimes": { | |
"nvidia": { | |
"path": "nvidia-container-runtime", | |
"runtimeArgs": [] | |
} | |
} | |
} |
it just worked for me, thanks!
Removing all networks first and leaving out the Nvidia config worked for me, thanks!
With the above solution, each time when connecting to WIFIonICE I was forced to remove networks created by docker compose again – which invalidated images and lead to running docker prune
way too often…
This works for a couple of months now, without the need to prune networks each time (only once after initial setup):
/etc/docker/daemon.json
{
"bip": "172.39.1.5/24",
"fixed-cidr": "172.39.1.0/25",
"default-address-pools":
[{
"base": "172.39.0.0/16",
"size": 24
}],
"runtimes": {
"nvidia": {
"path": "nvidia-container-runtime",
"runtimeArgs": []
}
}
}
Doesn't work for me =(
The address for docker0
complies, but the br-<somethin>
networks continue to use the 172.18.x.x range
Docker version 23.0.4, build f480fb1
Edit:
Ok, just got it working by running docker network prune
. Networks created after that will use the new range
Nice! 🚀
I had to delete all already existing container and images. After i did that, it worked.
Dear @sunsided,
I deleted existing networks with
docker network rm ...
first, then saved your snippet verbatim in/etc/docker/daemon.json
(I didn't have that file before).Afterwards, docker wouldn't work, i.e.
Running
sudo systemctl restart docker.service
didn't help either. I also tried it without the nvidia part:but the result was the same.