Yes. Here are the virtual hosts I've tried
redactedhost.local
redactedhost
pi.hole
Every one of the tests was run with the following command: docker stop pihole && rm -rf data/pihole/ && docker-compose up -d
The docker configuration is
pihole:
container_name: pihole
image: pihole/pihole:v5.7-stretch
ports:
- "9053:53/tcp"
- "9053:53/udp"
- "9080:80/tcp"
environment:
- VIRTUAL_HOST=pi.hole
env_file:
- ./.env.compose
- ./secrets/pihole/env
volumes:
- ./data/pihole/pihole:/etc/pihole
- ./data/pihole/dnsmasq:/etc/dnsmasq.d
restart: unless-stopped
And the env files have the following keys:
- WEBPASSWORD=redacted
- ADMIN_EMAIL=redacted@redacted.redacted
- PUID=500
- PGID=1000
- TZ=Asia/Kolkata
- UMASK_SET=022
(other containers in my compose file use these variables. Next up, I'll try removing them to see if it helps). I doubt it does because it was working last night with the same setup.
Absolutely. Plus this image worked last night. It's definitely something wrong with the host machine but I can't figure out what since I've changed the image and also deleted ./data/pihole
to reset it's state.
Any idea what this means from the docker logs?
$ docker logs -f pihole
[...]
[cont-init.d] 20-start.sh: executing...
::: Starting docker specific checks & setup for docker pihole/pihole
Failed to set capabilities on file `/usr/bin/pihole-FTL' (Operation not supported)
The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
I noticed a very similar issue when mounting /usr/bin
on a NFS. I'm running everything inside the docker container and nothing is mounted to /usr/bin
Update: Forgot to link the "very similar issue"