Disable systemd-resolved in Docker VM #2

Open
opened 2026-07-19 17:42:27 +07:00 by anton · 0 comments
Owner

And set 192.168.0.4 (Pi-hole) in /etc/resolv.conf

sudo systemctl stop systemd-resolved
sudo systemctl disable systemd-resolved
sudo systemctl stop systemd-resolved-monitor.socket
sudo systemctl disable systemd-resolved-monitor.socket
sudo systemctl stop systemd-resolved-varlink.socket
sudo systemctl disable systemd-resolved-varlink.socket
sudo systemctl mask systemd-resolved.service
sudo systemctl mask systemd-resolved-monitor.socket
sudo systemctl mask systemd-resolved-varlink.socket
sudo systemctl stop systemd-resolved
sudo unlink /etc/resolv.conf
And set `192.168.0.4` (Pi-hole) in `/etc/resolv.conf` ``` sudo systemctl stop systemd-resolved sudo systemctl disable systemd-resolved sudo systemctl stop systemd-resolved-monitor.socket sudo systemctl disable systemd-resolved-monitor.socket sudo systemctl stop systemd-resolved-varlink.socket sudo systemctl disable systemd-resolved-varlink.socket sudo systemctl mask systemd-resolved.service sudo systemctl mask systemd-resolved-monitor.socket sudo systemctl mask systemd-resolved-varlink.socket sudo systemctl stop systemd-resolved sudo unlink /etc/resolv.conf ```
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
anton/stacks#2
No description provided.