Replies: 2 comments 10 replies
-
My guess is there is a race condition on the 80 and 443 ports. by default Adguard will listen on 0.0.0.0 which means 'all IPs' - you want to force it to listen only on the new static IP you've set. I have adguard running in a similar fashion, I just used host networking instead for the container - it's 'risky' but it's the only service running in that jail right now. |
Beta Was this translation helpful? Give feedback.
-
I got it working. user args in my jail config systemd_nspawn_user_args=--network-bridge=br0
--system-call-filter='add_key keyctl bpf'
--bind='/mnt/tank/jailmaker/docker-data/pihole:/docker-data/pihole' |
Beta Was this translation helpful? Give feedback.
-
Hi,
i try to get Adguard Home running inside a jail.
Used the docker template and only changed the systemd_nspawn_user_args
/etc/resolv.conf inside the jail
Added a static IP like described here.
My compose.yaml
I can access the web interface via 192.168.0.10, but if i set the DNS on my router to 192.168.0.10 or direct to my Mac under Network Settings, no website will be loaded.
Any idea?
Beta Was this translation helpful? Give feedback.
All reactions