RD WebDesign

> any idea what is going wrong here when building the custom image? I think this is expected when the container is started without [`FTLCONF_dns_upstreams`](https://github.com/pi-hole/docker-pi-hole/?tab=readme-ov-file#recommended-environment-variables). https://github.com/pi-hole/docker-pi-hole/blob/8e04e6b2096d73a4a9432445b6816db34d22e5af/src/bash_functions.sh#L143-L147

> I then tried to do an `apt dist-upgrade` on the underlying host (ubuntu 22.04) and that also failed with a segmentation fault. This seems an OS/filesystem issue, completely unrelated...

@yubiuser About your comments above: > 1. On the dashboard, different upstream IPs with the same name are now displayed by name only. One cannot distinguish by IP anymore (select...

I need to test this PR again and check what is broken and what is working. I will try this later, after work.

@DL6ER @yubiuser Please check https://github.com/pi-hole/web/pull/3606

@4-FLOSS-Free-Libre-Open-Source-Software Did you try to set a DNS server for the container using the `dns:` option in your compose file? Try something like this: ```yml services: pihole: container_name: pihole image:...

> Shouldn't the update checker use FTL itself for its resolver? No. The container will use whatever DNS server is used by docker. Usually this is the DNS server configured...

> maybe it's enough to to show the first 50-100 lines or so. I thought the idea was to show **all** options in a single place. Showing just part of...

> I guess it will include the toml file once it builds but does not dynamically updates the content when the toml changes. Yes. We need to update the docs...

I don't think using this file is the best option. This file is used for **tests** and if, in the future, we decide to add invalid values in this file...