In another terminal, you can shell into the container and do an "htop" to check that dnsmasq will be using 100% of one CPU core.
I was able to reproduce this all the way back to Focal, but Bionic isn't impacted by this bug.
I believe it's worth trying to report it upstream and seeing if this rings any bells. I'm going to include this bug in our backlog; right now everybody from the Ubuntu Server team is busy with the upcoming Kinetic release.
mixmastamyk, if you feel like reporting this upstream please post the link to the email thread here so that we can keep an eye on it.
Thanks for the extra details, I was able to reproduce the problem here.
Here are the steps:
$ lxc launch ubuntu-daily:jammy dnsmasq-cpu-bug resolved. service
$ lxc shell dnsmasq-cpu-bug
# apt update
# apt install -y dnsmasq
# systemctl disable --now systemd-
# systemctl start dnsmasq.service
# dig gnu.org
In another terminal, you can shell into the container and do an "htop" to check that dnsmasq will be using 100% of one CPU core.
I was able to reproduce this all the way back to Focal, but Bionic isn't impacted by this bug.
I believe it's worth trying to report it upstream and seeing if this rings any bells. I'm going to include this bug in our backlog; right now everybody from the Ubuntu Server team is busy with the upcoming Kinetic release.
mixmastamyk, if you feel like reporting this upstream please post the link to the email thread here so that we can keep an eye on it.
Thanks.