pihole resolving, but unbound seems non reponsive?

[discorogge]

I hope you have time over for novice questions, i can't tell for certain that i understand how the image works, and because of this i feel like a burden. . ....pihole is ok and works, unbound seems to be offline if i check logs. My network is still fine tho, wich is wierd to me. i has docker-compose like so, with all my services, i used your dockerfile to start this up;

version: '3.0' volumes: etc_pihole-unbound: etc_pihole_dnsmasq-unbound: grafana_data: influxdb_data:

services: pihole: container_name: pihole image: cbcrowe/pihole-unbound:latest hostname: pihole domainname: pihole.local ports:

• 443:443/tcp
• 53:53/tcp
• 53:53/udp
• ${PIHOLE_WEBPORT:-80}:80/tcp #Allows use of different port to access pihole web interface when other docker containers use port 80
• 5335:5335/tcp # Uncomment to enable unbound access on local server

  - 22/tcp # Uncomment to enable SSH

  env_file: .env volumes:

• /opt/pihole/etc_pihole-unbound:/etc/pihole:rw
• /opt/pihole/etc_pihole_dnsmasq-unbound:/etc/dnsmasq.d:rw restart: unless-stopped -> env file is this:

standard

PUID=1000 PGID=1000 TZ=Europe/Stockholm

pihole / inbound

FTLCONF_LOCAL_IPV4=192.168.10.135 WEBPASSWORD=K----------------------- WEBTHEME=default-dark PIHOLEDNS=127.0.0.1#5335 DNSSEC="true" DNSMASQ_LISTENING=single*

This generates logs : ...... [i] Docker start setup complete Current Pi-hole version is v5.13 Current AdminLTE version is v5.16 Current FTL version is v5.18.2 Container tag is: [i] pihole-FTL (no-daemon) will be started as pihole s6-rc: info: service _startup successfully started s6-rc: info: service pihole-FTL: starting s6-rc: info: service pihole-FTL successfully started s6-rc: info: service lighttpd: starting s6-rc: info: service lighttpd successfully started s6-rc: info: service _gravityonboot: starting s6-rc: info: service _gravityonboot successfully started s6-rc: info: service legacy-services: starting Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf services-up: info: copying legacy longrun unbound (no readiness notification) s6-rc: info: service legacy-services successfully started Starting unbound [✗] DNS resolution is currently unavailable [i] Time until retry: 120 [i] Time until retry: 120 [i] Time until retr.........................

[discorogge]

I have brokened this myself by tinker'n in the docker-compose file . Do not mind me. My dock-comp file worked yesterday, i will backtrace my compose changers and find the problem. broke while tinker'n , Wife got problems when she got home so i had to change her dns resolver . . . I am very sorry for disturbing you.