Adguard home from truenas catalog: doesn`t work host network

Since the port binding feature was introduced, Adguard Home from the Truenas directory has been malfunctioning. DNS queries visible in Adguard’s webUI are from Docker’s internal network, which prevents client-based filtering. After enabling Host Network, the application stops working. Is there a solution?

The problem is partially solved. Disabling the pool in the containers menu solves the problem. However, we cannot use LXC virtualization. The problem is incus, which occupies port 53.

1 Like

Does changing the incus port cause any problems? For example, with LXC?

Not that I’ve noticed. If you run into an issue, you can change it back.