diff options
| author | Ahmed Abdelhalim <[email protected]> | 2025-08-21 03:24:34 +0200 |
|---|---|---|
| committer | Ahmed Abdelhalim <[email protected]> | 2025-08-21 03:24:34 +0200 |
| commit | 0f9de5e20c996ef231db505bbe18402c1ea7021e (patch) | |
| tree | 6f58f2b7f5f172d0ce62fe365159b88be47bb407 /roles/network | |
| parent | 22d1ae642daf7cc6b3f7897f50bac3941e336f5c (diff) | |
Fix the wireguard install
The conflict was due to resolvconf was removing the systemd-resolved
configuration and that was causing the network to go down and the
fallback on the statically managed resolv.conf (which wasn't able to
resolve the DNS) due to how network manager requiring the DNS resolution
to happen through systemd-resolved
Diffstat (limited to 'roles/network')
| -rw-r--r-- | roles/network/tasks/main.yml | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/roles/network/tasks/main.yml b/roles/network/tasks/main.yml index fd2553ff..c8c48268 100644 --- a/roles/network/tasks/main.yml +++ b/roles/network/tasks/main.yml @@ -54,12 +54,6 @@ - "Restart NetworkManager" - "Restart systemd-resolved" block: - - name: "Remove resolv.conf symlink" - ansible.builtin.file: - path: "/etc/resolv.conf" - state: "absent" - when: not ansible_is_chroot - - name: "Configure systemd-resolved" ansible.builtin.template: src: "resolved.conf.j2" |