You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
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.
The text was updated successfully, but these errors were encountered:
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
Related Issues
#1019
How to reproduce the issue
These common fixes didn't work for my issue
docker run
example(s) in the readme (removing any customizations I added)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.
The text was updated successfully, but these errors were encountered: