Use host's DNS resolver in Docker containers (#812)

* Symlink /etc/resolve.conf to systemd-resolved's stub

Since systemd-resolved is managing the DNS configuration, ensure that
/etc/resolv.conf uses it.

* Use systemd-resolved from Docker containers
This commit is contained in:
Kevin McConnell
2025-08-15 14:29:25 +01:00
committed by GitHub
parent 2db5e730a7
commit aca23ad834
4 changed files with 42 additions and 2 deletions

3
migrations/1754984623.sh Normal file
View File

@@ -0,0 +1,3 @@
echo "Ensure DNS resolver configuration is properly symlinked"
sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

21
migrations/1754984734.sh Normal file
View File

@@ -0,0 +1,21 @@
echo "Configure Docker to use the host's DNS resolver"
# If the daemon configuration has been changed since we wrote it, leave it as-is
ORIGINAL_CONFIG='{"log-driver":"json-file","log-opts":{"max-size":"10m","max-file":"5"}}'
NEW_CONFIG='{
"log-driver": "json-file",
"log-opts": { "max-size": "10m", "max-file": "5" },
"dns": ["172.17.0.1"],
"bip": "172.17.0.1/16"
}'
if grep -Fq "$ORIGINAL_CONFIG" /etc/docker/daemon.json 2>/dev/null; then
echo "$NEW_CONFIG" | sudo tee /etc/docker/daemon.json >/dev/null
fi
# Expose systemd-resolved to our Docker network
echo -e '[Resolve]\nDNSStubListenerExtra=172.17.0.1' | sudo tee /etc/systemd/resolved.conf.d/20-docker-dns.conf >/dev/null
sudo systemctl restart systemd-resolved
sudo systemctl restart docker