Dnsmasq should start at boot and just not care about docker specific interfaces.

This commit is contained in:
Samuel Clay 2024-02-08 19:11:12 -05:00
parent fd1346af7e
commit e9b69a634f
2 changed files with 14 additions and 8 deletions

View file

@ -80,14 +80,20 @@
state: directory
mode: 0755
- name: Add override for dnsmasq service
become: yes
copy:
dest: /etc/systemd/system/dnsmasq.service.d/override.conf
content: |
[Unit]
After=docker.service
# - name: Add override for dnsmasq service
# become: yes
# copy:
# dest: /etc/systemd/system/dnsmasq.service.d/override.conf
# content: |
# [Unit]
# After=docker.service
- name: Remove override for dnsmasq service
become: yes
file:
path: /etc/systemd/system/dnsmasq.service.d/override.conf
state: absent
- name: Launch dnsmasq
become: yes
service:

View file

@ -9,7 +9,7 @@ server=/consul/127.0.0.1#8600
no-resolv
{% for interface in network_interfaces %}
{% if not interface.startswith('veth') %}
{% if not interface.startswith('veth') and not interface.startswith('docker') and not interface.startswith('br') %}
interface={{ interface }}
{% endif %}
{% endfor %}