_Docker Daemon
These configs have stumped me one too many times.
Issue: Why is my docker host having trouble resolving DNS?After enabling pi-hole or other dockerized DNS management app, lack of (systemd-resolved e.t.c. means that DNS is not available on a local level prior to docker to so much as pull pi-hole. (wonderful chick needs to lay its own egg scenario) A great solution I found to this issue is to set the DNS for docker explicitly.
Issue: Why aren't the nvidia drivers workable on my system.Gotta love the oversight, better remember to request gpu here as well as in the compose. 🤦♀️
Issue: After creating about 40 stacks / docker containers ... I can no longer create new ones with unique ips...As seen below we need to set/allow additional ranges of IP addresses for docker to use in addition to those available by default. You can use something like below or adjust to a set of IPs not taken elsewhere on your network.
{
"runtimes": {
"nvidia": {
"args": [],
"path": "nvidia-container-runtime"
}
},
"default-address-pools" : [
{
"base" : "172.50.0.0/12",
"size" : 20
},
{
"base" : "192.168.30.0/16",
"size" : 24
}
],
"dns": ["<pihole#1>", "<pihole#2>", "1.1.1.1", "8.8.8.8"]
}
Note:
Later when I describe how to setup pihole remind me to note that we need to turn off that below and update the dns for docker.
Pi-Hole
sudo systemctl stop systemd-resolved
No Comments