"development-v6" branch seems to cause issues with unRAID (or vice versa)

I posted as a reply in the Reddit announcement thread, and was told to post here.

unRAID version: 6.12.4 (latest as of writing)

Installed via the community applications / apps plugin.
Changed branch from latest to development-v6
Updated variables according to the docs AFAICT

unRAID fails to show port mappings and also seems to fail getting the container's IP as the WebUI option (which forwards to container webui) seems to not work. This only seems to happen with dev-v6.

docker network inspect br0:

            "7afc9d3393bd8f109248f9503eb0cb99eaf2e4153488a5d7115db3a94f9c18d9": {
                "Name": "pihole-v6",
                "EndpointID": "f9b5f3bff277372c81ed465fed35a9562619fe7283b64ed936d9c181df6d2013",
                "MacAddress": "02:42:c0:a8:0a:16",
                "IPv4Address": "192.168.10.22/24",
                "IPv6Address": "2003:ea:bf46:55e6::3/64"
            }

docker run command:

 docker run
   -d
   --name='pihole-v6'
   --net='br0'
   --ip='192.168.10.22'
   -e TZ="Europe/Berlin"
   -e HOST_OS="Unraid"
   -e HOST_HOSTNAME="Skipper"
   -e HOST_CONTAINERNAME="pihole-v6"
   -e 'TCP_PORT_53'='53'
   -e 'UDP_PORT_53'='53'
   -e 'UDP_PORT_67'='67'
   -e 'TCP_PORT_80'='80'
   -e 'TCP_PORT_443'='443'
   -e FTLCONF_dns_upstreams'='1.1.1.1;1.0.0.1;2606:4700:4700::1111;2606:4700:4700::1001;8.8.8.8;8.8..;2001:4860:4860:0:0:0:0:8888;2001:4860:4860:0:0:0:0:8844'
   -e 'TZ'='Europe/Berlin'
   -e 'FTLCONF_webserver_api_password'='admin'
   -e 'INTERFACE'='br0'
   -e 'ServerIP'='192.168.10.22'
   -e 'ServerIPv6'='fd01:c989:1699:1:42:c0ff:fea8:a16'
   -e 'IPv6'='True'
   -e 'DNSMASQ_LISTENING'='all'
   -e 'WEBUIBOXEDLAYOUT'='boxed'
   -l net.unraid.docker.managed=dockerman
   -l net.unraid.docker.webui='http://[IP]:[PORT:80]/admin'
   -l net.unraid.docker.icon='https://i.imgur.com/OWkNcEn.png'
   -v '/mnt/disk1/appdata/pihole-v6/pihole/':'/etc/pihole/':'rw'
   -v '/mnt/disk1/appdata/pihole-v6/dnsmasq.d/':'/etc/dnsmasq.d/':'rw'
   --cap-add=NET_ADMIN
   --restart=unless-stopped 'pihole/pihole:development-v6'
 7afc9d3393bd8f109248f9503eb0cb99eaf2e4153488a5d7115db3a94f9c18d9

Debug token of the container, if it helps / matters:

https://tricorder.pi-hole.net/4aIpcmYB/

If any other info is needed, let me know!

Thanks, and I hope y'all have a nice day :slight_smile:

This is not how you should publish ports in Docker.

You need to use -p option: Networking overview | Docker Docs

Might be different in unraid, not sure.

However these will not work with v6

They need to be replaced with relevant FTLCONF_ variables

This is the template of the PiHole container on unRAID: https://raw.githubusercontent.com/spants/unraidtemplates/master/Spants/pihole.xml

This template was created by a third party (GitHub - spants/unraidtemplates) and it was based on the v5 configuration.

v6 uses a complete different set of environment variables. You need to use/create a new template.

I can see the variable name through all configs in the expert level, right?

Say, FTLCONF_dns.interface?

Yeah, that's it. You can also look inside pihole.toml, or the web API docs at Pi-hole API documentation

Seems specifying these isn't strictly needed anymore as PH tries to figure this out by itself now? (force4, force6 description)

Trimmed it down to

docker run
  -d
  --name='pihole-v6-2'
  --net='br0'
  --ip='192.168.10.22'
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Skipper"
  -e HOST_CONTAINERNAME="pihole-v6-2"
  -e 'TCP_PORT_53'='53'
  -e 'UDP_PORT_53'='53'
  -e 'UDP_PORT_67'='67'
  -e 'TCP_PORT_80'='80'
  -e 'TCP_PORT_443'='443'
  -e 'FTLCONF_dns_upstreams'='1.1.1.1;1.0.0.1;2606:4700:4700::1111;2606:4700:4700::1001;8.8.8.8;8.8.4.4;2001:4860:4860:0:0:0:0:8888;2001:4860:4860:0:0:0:0:8844'
  -e 'TZ'='Europe/Berlin'
  -e 'FTLCONF_webserver_api_password'='admin'
  -e 'FTLCONF_dns.interface'='br0'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:80]/admin'
  -l net.unraid.docker.icon='https://i.imgur.com/OWkNcEn.png'
  -v '/mnt/disk1/appdata/pihole-v6-2/pihole/':'/etc/pihole/':'rw'
  -v '/mnt/disk1/appdata/pihole-v6-2/dnsmasq.d/':'/etc/dnsmasq.d/':'rw'
  --cap-add=CHOWN
  --cap-add=SYS_NICE
  --restart=unless-stopped 'pihole/pihole:development-v6'
0931dca4453ed34aacf502bd88bad25b6bd85cf9a15a9704c7b6d989192139d9

unRAID's port mapping etc still seems borked though.. Can't wrap my head around this one. Or rather why it works in both latest and nightly but not dev-v6

Container log, which is starting to clear up: Untitled | Pastey

As for earlier, I don't know why this template sets ports as env variables, in the web ui it's labeled as "Port" instead of "Variable" - but I'm sure there's a reason for this? Container itself functions so I guess it's fine

In v5 ServerIP was replaced a long time ago by FTLCONF_LOCAL_IPV4 (Recommended Variables).

I think the similar config in v6 is FTLCONF_dns_reply_host_IPv4.