The first run got stuck as follows.
Restart Docker Compose
Docker may have omitted to inject your host's resolv.conf into your container, or that file points to nameservers that are unavailable from the container.
That should be addressed by passing a public DNS server into your container, to be used by the container itself:
services:
(…)
pihole:
ports:
(…)
dns:
- 1.1.1.1
(…)
Note that this standard Docker element is different from Pi-hole's own upstream DNS servers, as definable via your Pi-hole container's FTLCONF_dns_upstreams environment variable.
The configuration is as follows
# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
services:
pihole:
container_name: pihole
#image: pihole/pihole:development
image: pihole/pihole:latest
hostname: Pi-hole
restart: always
networks:
- docker-net
ports:
# DNS Ports
- "53:53/tcp"
- "53:53/udp"
# Default HTTP Port
- "5380:80/tcp"
environment:
- TZ=Asia/Shanghai
- FTLCONF_webserver_api_password=admin123
- FTLCONF_dns_upstreams=169.254.0.254#5335
- FTLCONF_dns_listeningMode=all
- FTLCONF_misc_dnsmasq_lines=server=/xxx.com/192.168.248.1;no-0x20-encode
volumes:
# For persisting Pi-hole's databases and common configuration file
- "./etc-pihole:/etc/pihole"
# Uncomment the below if you have custom dnsmasq config files that you want to persist. Not needed for most.
# - "./etc-dnsmasq.d:/etc/dnsmasq.d"
networks:
docker-net:
external: true
That's (still) missing the dns element.
DNS has been added
Maybe due to the lack of communication with GitHub, the default 'StevenBlack' cannot be downloaded
Can the list not be loaded through environment variables
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.