Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DEBUG_ANY dnsmasq received signal 17 #1667

Open
6 tasks done
PatricioooAG opened this issue Dec 2, 2024 · 1 comment
Open
6 tasks done

DEBUG_ANY dnsmasq received signal 17 #1667

PatricioooAG opened this issue Dec 2, 2024 · 1 comment

Comments

@PatricioooAG
Copy link

PatricioooAG commented Dec 2, 2024

This is a: Run issue

Details

Im using the nightly image, the problem are with the latest releases of Docker Desktop, after a minutes I get the log : DEBUG_ANY dnsmasq received signal 17 and the webs are not loading. I have in the compose to make a local folder PiHole and dnsmasq, but dnsmasq folder is always empty and I don't know if is normal. The problem is the same with "latest" image, I try too the different virtualization modes in Docker. It's my second time writing for help, but the dnsmasq log is new. The latest Docker Desktop working are 4.17 maybe to 4.19, newer don't. Thanks.

Related Issues

  • I have searched this repository/Pi-hole forums for existing issues and pull requests that look similar

How to reproduce the issue

  1. Environment data
  • Operating System: MacOs
  • Hardware: MacBook Pro M3
  • Kernel Architecture:
  • Docker Install Info and version:
    • Software source:
    • Supplimentary Software:
  • Hardware architecture:
  1. docker-compose.yml
version: '3'
services:
  pihole:
    image: pihole/pihole:nightly
    container_name: pihole
    environment:
      - ServerIP=10.0.0.18
      - TZ=Europe/Madrid
      - DNS1=10.0.0.18:5053  # Apuntamos al servidor DoH en 10.0.0.18:5053
    ports:
      - "8082:80"
      - "10.0.0.18:53:53/tcp"
      - "10.0.0.18:53:53/udp"
      - "448:443"  # Puerto HTTPS para la interfaz web
    volumes:
      - ./pihole:/etc/pihole    # Persistencia de configuración de Pi-hole
      - ./dnsmasq:/etc/dnsmasq.d # Persistencia de configuración de dnsmasq
    dns:
      - 1.1.1.1               # DNS de Docker para la resolución interna
    restart: unless-stopped   # Reiniciar el contenedor en caso de fallo
    cap_add:
      - SYS_TIME
    depends_on:
      - cloudflared

  cloudflared:
    image: crazymax/cloudflared:latest
    container_name: cloudflared
    ports:
      - '5053:5053/udp'
      - '5053:5053/tcp'
    environment:
      - "TZ=Europe/Madrid"
      - "TUNNEL_DNS_UPSTREAM=https://1.1.1.1/dns-query,https://1.0.0.1/dns-query"
    restart: always

volumes:
  pihole:
  dnsmasq:
  1. any additional info to help reproduce
    wait some time.

These common fixes didn't work for my issue

  • I have tried removing/destroying my container, and re-creating a new container
  • I have tried fresh volume data by backing up and moving/removing the old volume data
  • I have tried running the stock docker run example(s) in the readme (removing any customizations I added)
  • I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me)
  • I have tried running without my volume data mounts to eliminate volumes as the cause

If the above debugging / fixes revealed any new information note it here.
Add any other debugging steps you've taken or theories on root cause that may help.

@PromoFaux
Copy link
Member

DNS1=10.0.0.18:5053 # Apuntamos al servidor DoH en 10.0.0.18:5053

This wont work on the nightly image, which is now based on Pi-hole v6.

Please take a look over the draft v6 docs here which has a section on Docker and upgrading from v5: https://deploy-preview-338--pihole-docs.netlify.app/docker/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants