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

Stop working in latest release. #1578

Open
1 task
PatricioooAG opened this issue May 11, 2024 · 0 comments
Open
1 task

Stop working in latest release. #1578

PatricioooAG opened this issue May 11, 2024 · 0 comments

Comments

@PatricioooAG
Copy link

I try to install the latest releases of Docker but after a few hours PiHole stop working, and I need update Gravity or restart the container. The last release I can use fine is 17. I don’t getting error in console.

This is a: FILL ME IN
Run issue

Details

Related Issues

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

I know VirtioFS have permission problem but I can’t get too much info.

How to reproduce the issue

  1. Environment data
  • Operating System: ENTER HERE MacOs Sonoma
  • Hardware: Mac M series
  • Kernel Architecture:
  • Docker Install Info and version:
    • Software source:
    • Supplimentary Software:
  • Hardware architecture:
  1. docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here docker run -d --name pihole -e ServerIP=10.0.0.1 -e TZ=Europe/Madrid -e DNS1=10.0.0.1 -p 8087:80 -p 10.0.0.18:53:53/tcp -p 10.0.0.18:53:53/udp -p 443:443 -v ~/pihole/:/etc/pihole/ -v ~/dnsmasq.d:/etc/dnsmasq.d --dns=127.0.0.1 --dns=127.0.0.1 --dns=1.1.1.1 --restart=unless-stopped pihole/pihole:latest
  2. any additional info to help reproduce

These common fixes didn't work for my issue

I try different sharing implementation like VirtioFS and gRPC FUSE. I try too without virtualization on and off.
  • [x ] I have tried removing/destroying my container, and re-creating a new container
  • [ x] 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)
  • [x ] I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me)
  • [ x] 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.

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

1 participant