Pi-hole container not working

[rdwebdesign]

There are 2 things happening here.

1. Docker Desktop volume issue:

I think you have the same issue described in this topic:

Sed: couldn't open temporary file /etc/pihole/sed***

I'm not a Docker or sed expert, but I tried to find what is the issue. Maybe someone with more knowledge on these fields could correct me if I'm wrong. Apparently there is a problem between sed 4.7 and the filesystem used by Docker Desktop (MacOS and Windows). Pi-hole image uses sed 4.7 (from Debian Bullseye). Some sed versions (>= 4.2.1 and < 4.8) have a problem with temporary files permissions in some filesystems. You are using a bind mount to your MacOS filesystem (I think Docker Desktop…

There is an issue between sed (running inside the container) and the filesystem used to store the volumes used by Docker Desktop (MacOS and Windows), causing a permission issue:

@joaocasarin

sed: couldn't open temporary file /etc/pihole/sedcRHggR: Permission denied

Please read the topic above and change your compose file accordingly.

2. Wrong ports:

@joaocasarin

        ports:
            - 5333:53/tcp
            - 5333:53/udp

These ports won't work. You need to configure 53:53/tcp and 53:53/udp.
You also need to disable the service using port 53 on the host.

Your devices will send DNS queries only to port 53 (they have no idea there is a DNS server at port 5333).
If you use these ports, no devices will be able to use Pi-hole.