dnsmasq: listen addresses are a setting, and docker's file takes none (hq issue 198) #214

Merged
mesh-admin merged 1 commits from jschoubben/the-lans-dns-is-the-mesh-2 AGit into main 2026-10-02 09:50:09 +00:00
Owner

Redo of PR 212 (reverted in 213) with the fault fixed. listen-address=${setting:listen-addresses} in dnsmasq's config. Docker's daemon.json loses merge: json, so no setting of the module reaches it; it keeps into: json, so the host still merges its keys into the existing file (dhcpcd's config takes into without merge the same way). Settings are set only after this lands: until then the dnsmasq machines are refused composition, which sends nothing.

Redo of PR 212 (reverted in 213) with the fault fixed. listen-address=${setting:listen-addresses} in dnsmasq's config. Docker's daemon.json loses merge: json, so no setting of the module reaches it; it keeps into: json, so the host still merges its keys into the existing file (dhcpcd's config takes into without merge the same way). Settings are set only after this lands: until then the dnsmasq machines are refused composition, which sends nothing.
jschoubben added 1 commit 2026-10-02 09:49:58 +00:00
The addresses dnsmasq listens on beside the machine's are a setting, so a
machine that answers its own LAN can say so (novox/hq issue 198). Docker's
daemon.json no longer merges the module's settings: it needs none, and a
setting reaching it is a key dockerd refuses. The host still merges it
into the existing file.
mesh-admin merged commit 3020cd2312 into main 2026-10-02 09:50:09 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#214