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

pihole on docker not starting anymore #1145

Closed
6 tasks done
Darkmagister opened this issue Jul 14, 2022 · 3 comments
Closed
6 tasks done

pihole on docker not starting anymore #1145

Darkmagister opened this issue Jul 14, 2022 · 3 comments

Comments

@Darkmagister
Copy link

Darkmagister commented Jul 14, 2022

This is a: Run Issue

Details

i have docker v 20.10.17 on my nas, and pihole latest image, few days ago i noticed that i have issue in starting the container, i've tried few solution found here (adding net_admin cap to the container, setting the dnsmasq user to root, reverting back to an older image of pihole) but nothing worked
i get this error

Starting pihole-FTL (no-daemon) as root
Stopping pihole-FTL
pihole-FTL: no process found
Starting pihole-FTL (no-daemon) as root
Stopping pihole-FTL
pihole-FTL: no process found
Starting pihole-FTL (no-daemon) as root
Stopping pihole-FTL
pihole-FTL: no process found

Related Issues

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

#1019

How to reproduce the issue

  1. Environment data
  • Operating System: linux asustor nas
  • Hardware: asustor nas
  • Kernel Architecture: amd64
  • Docker Install Info and version:
    • Software source: 20.10.17
    • Supplimentary Software: portainer
  • Hardware architecture: amd64
  1. docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
  2. any additional info to help reproduce

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

PromoFaux commented Jul 14, 2022

Might be to do with this? #1042 (comment)

@PromoFaux
Copy link
Member

Also, do you have something else (host, another container?) listening on port 53? That can cause issues, too.

@Darkmagister
Copy link
Author

Also, do you have something else (host, another container?) listening on port 53? That can cause issues, too.

yes that was the issue i had a subsystem ubuntu with a resolver at port 53 ... disabling it now pihole work again thanks

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