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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.