Ok, I switched to bridge network and the correct port settings do appear! Thanks for explaining.

How I can set the PiHole IP now? The option is not available in bridge mode.

Is switching to the FTLCONF_dns_listeningMode: 'ALL' variable is correct in the run command below?

Edited June 3Jun 3 by Anti-Matt-er

On 6/2/2026 at 3:04 AM, tjb_altf4 said:

Switch to bridge network and right port settings will reappear.
You can't port map on custom networks like the docker br0, so either you can have pihole on its own IP with no mapping (ports are 1:1), or you can use the port mapping like the pihole devs suggest.

I think I want the PiHole on it's own IP with no mapping, but I don't know how to set the IP for the container. There was an IP field previously, but with the settings you recommended it disappeared. Is there a variable that I can add? I tried a few things but all of them failed at run.

Thanks!

1 hour ago, Anti-Matt-er said:

I think I want the PiHole on it's own IP with no mapping, but I don't know how to set the IP for the container. There was an IP field previously, but with the settings you recommended it disappeared. Is there a variable that I can add? I tried a few things but all of them failed at run.

Thanks!

Change to a custom network like br0, then the IP field appears again. Be sure to set an IP outside your router's DHCP range so it doesn't create a conflict later on.

17 hours ago, strike said:

Change to a custom network like br0, then the IP field appears again. Be sure to set an IP outside your router's DHCP range so it doesn't create a conflict later on.

Ok, instructions followed. I was able to change it back and set the IP.

Now the port variables I was told by the PiHole team should be -p are back to -e. Is that correct? I'm not seeing the errors I was previously so I'm hoping the config is correct, even if it differs from what they recommended.

There was a security incident for AUR (Arch User Repository) where a number of packages were compromised (see the list of packages affected here), i have done a thorough scan of all my docker images and found zero references to the affected packages, so i believe all images are clean at this time.