Open simondeziel opened 3 months ago
If there is no problem I will assign this to myself
That happens because the way we update host entries on dnsmasq
is by sending a SIGHUP
signal to the dnsmasq
process. That makes it restart and read all the entries again from dnsmasq.hosts
. The only viable alternative to that would be to use the flag --hostsdir
instead of --dhcp-hostsfile
, that way dnsmasq automatically updates created and modified entries inside the specified directory (but apparentely not removed ones, so it isn't a perfect solution).
I took some time to test the usage of --hostsdir
and it seems like it solves the problem even when deleting instances/removing entries. Even so, it seems too risky to use that flag without further investigation.
Creating an instance causes
dnsmasq
to log one line for each of the existing/known instances in every projects. This can snowball as you create more instances over time. Here's how to reproduce it:Which causes the following to be logged:
journald
stores more than just the log message which means more data needs to be saved to disk. While a flawed approximation, the JSON exported logs for that repeated messages alone weights ~100KiB: