Did a new docker pull and now pihole wont start.
ANY help would be greatly appreciated. Thanks
Please post your docker-compose.yml or your docker run commands.
Since you run Docker via Portainer:
Portainer may hold on to environment values from previous containers even on container restart. If this would create issues for you, you'd have to manually remove offending environment variables.
See how this was resolved in Pihole Portainer/Docker 5.8.1 startup error?.
Tried this, but didnt work.
When I run debug I still get:
** [ DIAGNOSING ]: Pi-hole processes
[✗] lighttpd daemon is inactive
[✗] pihole-FTL daemon is inactive
Your debug log still reports your Pi-hole Docker container as 2022.01.1.
That release tag would have comprised Pi-hole v5.8, FTL v5.13, Web Interface v5.10, but your debug log reveals those to match the current Pi-hole v5.10, FTL v5.15, Web Interface v5.12.
Please be more specific how you followed that solution suggestion:
Which variables did you actually clobber?
Tempted to just recreate from scratch
unless solving this helps someone else in the future
It looks like you've only removed the values, not the variables themselves.
Also, did you recreate the container after deleting those values?
I'm not using Portainer myself - someone familiar with Portainer may be able to provide more specific advice, so it may be a good idea to mention Portainer in your topic's title.
No, I did remove the values. Just used above as visual cue to what I removed
https://tricorder.pi-hole.net/gfXit1wy/
Following this thread : Docker on Synology keeps stopping with Failed to set capabilities for pihole-FTL. Cannot run as non-root. · Issue #963 · pi-hole/docker-pi-hole (github.com)
I tried adding PUID and PGID to environment variables and at least PIHOLE_DOCKER_TAG updated to correct tag: 2022.04.3
Still not starting though
Sorry for being pedantic, but do you mean values here?
If so, try removing the variables and Recreate the container afterwards.
Do you see the same error as in the issue in your Docker logs then?
ERROR: Failed to set capabilities for pihole-FTL. Cannot run as non-root.
EDIT: If you did encounter the same error, still note that you've applied an arbitrary suggestion for a fix that has worked for one user (which just happened to be the last post at the time you've accessed that issue).
That rather lengthy issue does contain other solution approaches that received positive confirmation from more than just one user.
They would be pretty much comprised in our Docker Pi-hole Upgrade Notes.
Could you check your Docker log for failures and share it here?
Figured it out
I must have used macvlan before, and didnt use again.
Set it up via Network in Portainer, and now working again
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.