Tom Parrott
Tom Parrott
Actually that PR https://github.com/lxc/lxd/pull/9750 didn't change the act of kill the process if the control socket disconnected, so thats not the change. Looks like a while back it ignored every...
@cjwatson can I confirm what version of the `lxc` comand you're using? `lxc --version`?
@cjwatson also if you add a local TCP remote such as `lxc remote add localtcp 127.0.0.1` (you might need to configure LXD to listen on that port `lxc config set...
I suppose if you can capture (the ableit encrypted) TCP stream `tcpdump -nn -i lo port 8443` then we can 100% confirm that the client is closing the control connection....
@cjwatson are you still experiencing this with LXD 5.0?
Will do.
@jgneff most likely its not systemd-networkd setup causing problem but instead this issue that was preventing dnsmasq from starting when using `raw.dnsmasq` network setting, see https://github.com/lxc/lxd/issues/8905
In that case check your system firewall its likely some external rules are inferring with lxds dhcp server, likely caused by it refreshing and reloading causing it to clear and...
Take a look at this https://discuss.linuxcontainers.org/t/lxd-bridge-doesnt-work-with-ipv4-and-ufw-with-nftables/10034/17 (as you can see its not a new issue) If you can send a pull request for that it would be great if not...
Glad that's working. This may have been the sudden cause of your issue, the snap core20 change subtly affected the cases where nftables would be used https://discuss.linuxcontainers.org/t/lxd-stopped-generating-firewall-rules-after-switch-to-core20/11367/9?u=tomp