-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Description
Prerequisites
-
I have checked the Wiki and Discussions and found no answer
-
I have searched other issues and found no duplicates
-
I want to request a feature or enhancement and not ask a question
The problem
When running Adguard Home with rootless Podman, netavark is used as the network stack. In that case, the container is not able to see the real client IP. To the Adguard container it looks like every request is coming from the same client.
Proposed solution
One way for a rootless container to see the real client IP would be systemd socket activation. Podman has support for it. However, Adguard Home currently does not seem to support socket activation.
Alternatives considered and additional information
Besides seing the real client ip, this would also allow activation of Adguard on incoming network requests as well as native network performance for rootless containers.