Questions concerning [How To] Install Pi-Hole in Docker

Zitat von tinh_x7

I made several attempts with installed PiHole, but it failed.
Some crap permissions issue that I can't figure it ou

I've never had a problem with OMV4. Are you attempting to install on OMV5?

Zitat von loso

anybody can help me with pihole/docker/macvlan?

First, tell me you're not using WatchTower.

Give me a day or so. I haven't installed/reinstalled pi-hole in a Docker lately (in OMV4). I'll run through it again.
Sometimes they change the container which may necessitate changing some of the variables.

My gripe with WatchTower is that it can (and does) update pi-hole containers without bridging over Pi-holes admin webpage settings (if altered from default). New pi-hole Docker images may require new variables, meaning Watchtower creates the potential to crash your LAN's DNS resolution without notice.

And, frankly, I don't know what else it does as it "swaps" out images and containers.
______________________________________________________________

The following was done on an amd64 platform:

Following the existing How-To exactly as written, start to finish;

- Set up a public DNS server in OMV.
- Deleting all (as recommended) items related to the old container.
- Delete the directory and contents of /dockerparms.
- Then follow the How-To exactly.
(Pull a new pihole/pihole image, etc., etc.)

After 3 minutes, I logged into the console - 192.168.1.X/admin.
I tested DNS and blocking, using one my WIndows clients with a custom DNS entry (pi-holes IP).

It worked with no problems, and is acting as the DNS server for this post.

**Edit: Just to cover all the bases, I brought the amd64 platform fully up-to-date to insure there's no issues or conflicts in Debian or in OMV.**

There is one consideration that needs further checks and testing:

For those who are Blocking all IPv6 using the file pihole-FTL.conf under /dockerparms/pihole/
Delete the file pihole-FTL.conf

The file "seems" to be causing the pi-hole container to continually restart. More when known.

Until then, universal IPv6 blocking is being removed from the How-To.

Zitat von migue789

I still can't open web page pihole attached log.

The first thing that jumps out, from the log, is the following:

[?] DNS resolution is currently unavailable

Since pi-hole is a DNS proxy, it won't work without being able to resolve remote servers.

Then:
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

What are you using for setting up Pihole?

Zitat von migue789

now it indicates the dead state, help? thanks.

Restart policy should be set to always, and in the image docker1 you have not entered an IP address for Pi-Hole, but in docker2 in environment variables you have added one.