2022.08 not starting on Synology NAS #1175
Comments
|
Seems that this might be the same issue as #1085 as that was based on |
|
I can't see that anything has changed to require it... (and interestingly I haven't needed to add this on my own Synology install)
You can try adding https://github.com/pi-hole/docker-pi-hole#note-on-capabilities |
|
@PromoFaux Didn't work for me in the compose file: cap_add:
- NET_ADMIN # Recommended but not required (DHCP needs NET_ADMIN)
- CAP_CHOWN |
|
Having the same issue. |
|
Same issue. I downgraded to 2022.07.1 and now it works again. |
|
having same issue on QNAP |
|
Pihole not starting on my raspberryPi downgraded to 2020.07.01 |
|
@ramonsmits I'm not sure what to say here... using your compose file (tweaked to use What does |
It works for you because you are using btrfs |
|
So I guess the question is ultimately:
The major difference here is the version of S6 overlay that we are using. There is also a change to where the caps are being set. Old it was as the first thing the container did in Hold my beer... |
|
Bit of a stab in the dark, but please try the |
|
👍🏼 The dev tag works for me |
|
@rober3847 did you have the same issue that was reported by OP? @ramonsmits, @Insectodium, @dvdstelt, @daNutzzzzz (any anyone else that reported seeing this issue) Please try |
|
Yes - 2022.7.1 was working but when I tried 2022.8 on my Synology - pihole would not start. pihole-FTL: no process found Using the same compose file both 2022.7.1 and the new dev version start successfully |
@PromoFaux I tried pihole2 | s6-rc: info: service cron: starting
pihole2 | s6-rc: info: service s6rc-oneshot-runner: starting
pihole2 | Starting crond
pihole2 | s6-rc: info: service cron successfully started
pihole2 | s6-rc: info: service s6rc-oneshot-runner successfully started
pihole2 | s6-rc: info: service fix-attrs: starting
pihole2 | s6-rc: info: service _startup: starting
pihole2 | fix-attrs: info: applying /etc/fix-attrs.d/01-resolver-resolv
pihole2 | fix-attrs: warning: fix-attrs is deprecated, please fix volume permissions in your container manager instead
pihole2 | s6-rc: info: service fix-attrs successfully started
pihole2 | s6-rc: info: service legacy-cont-init: starting
pihole2 | cont-init: info: running /etc/cont-init.d/05-changer-uid-gid.sh
pihole2 | cont-init: info: /etc/cont-init.d/05-changer-uid-gid.sh exited 0
pihole2 | ::: Starting docker specific checks & setup for docker pihole/pihole
pihole2 | s6-rc: info: service legacy-cont-init successfully started
pihole2 | Failed to set capabilities on file `/usr/bin/pihole-FTL' (Operation not supported)
pihole2 | The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
pihole2 |
pihole2 | [i] Installing configs from /etc/.pihole...
pihole2 | [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
[✓] Installed /etc/dnsmasq.d/01-pihole.conf
[✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
pihole2 |
pihole2 | [i] Installing latest logrotate script...
pihole2 | [i] Existing logrotate file found. No changes made.
pihole2 | Custom WEB_PORT set to 889
pihole2 | INFO: Without proper router DNAT forwarding to 0.0.0.0:889, you may not get any blocked websites on ads
pihole2 | ::: Assigning password defined by Environment Variable
pihole2 | [✓] New password set
pihole2 | Added ENV to php:
pihole2 | "TZ" => "Europe/Amsterdam",
pihole2 | "PIHOLE_DOCKER_TAG" => "dev",
pihole2 | "PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log",
pihole2 | "CORS_HOSTS" => "",
pihole2 | "VIRTUAL_HOST" => "0.0.0.0",
pihole2 | Using IPv4 and IPv6
pihole2 | ::: setup_blocklists now setting default blocklists up:
pihole2 | ::: TIP: Use a docker volume for /etc/pihole/adlists.list if you want to customize for first boot
pihole2 | ::: Blocklists (/etc/pihole/adlists.list) now set to:
pihole2 | https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
pihole2 | Existing DNS servers detected in setupVars.conf. Leaving them alone
pihole2 | Applying pihole-FTL.conf setting LOCAL_IPV4=0.0.0.0
pihole2 | FTL binding to default interface: eth0
pihole2 | ::: Enabling Query Logging
pihole2 | ::: Testing lighttpd config: Syntax OK
pihole2 | ::: All config checks passed, cleared for startup ...
pihole2 | ::: Docker start setup complete
pihole2 | Pi-hole version is v5.11.4 (Latest: v5.11.4)
pihole2 | AdminLTE version is v5.13 (Latest: v5.13)
pihole2 | FTL version is v5.16.3 (Latest: v5.16.3)
pihole2 | Container tag is: dev
pihole2 | s6-rc: info: service _startup successfully started
pihole2 | s6-rc: info: service pihole-FTL: starting
pihole2 | s6-rc: info: service pihole-FTL successfully started
pihole2 | s6-rc: info: service _gravityonboot: starting
pihole2 | s6-rc: info: service lighttpd: starting
pihole2 | Starting pihole-FTL (no-daemon) as root
pihole2 | s6-rc: info: service lighttpd successfully started
pihole2 | s6-rc: info: service _gravityonboot successfully started
pihole2 | Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
pihole2 | s6-rc: info: service legacy-services: starting
pihole2 | Starting lighttpd
pihole2 | s6-rc: info: service legacy-services successfully started
pihole2 | [i] Neutrino emissions detected...
[✓] Pulling blocklist source list into range
pihole2 |
[✓] Preparing new gravity database
pihole2 | [i] Using libz compression
pihole2 |
pihole2 | [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
[✓] Status: Retrieval successful
pihole2 | [i] Analyzed 136495 domains
pihole2 | [i] List stayed unchanged
pihole2 |
[✓] Creating new gravity databases
[✓] Storing downloaded domains in new gravity database
[✓] Building tree
[✓] Swapping databases
pihole2 | [✓] The old database remains available.
pihole2 | [i] Number of gravity domains: 136495 (136495 unique domains)
pihole2 | [i] Number of exact blacklisted domains: 0
pihole2 | [i] Number of regex blacklist filters: 0
pihole2 | [i] Number of exact whitelisted domains: 0
pihole2 | [i] Number of regex whitelist filters: 0
[✓] Cleaning up stray matter
pihole2 |
pihole2 | [✓] FTL is listening on port 53
pihole2 | [✓] UDP (IPv4)
pihole2 | [✓] TCP (IPv4)
pihole2 | [✓] UDP (IPv6)
pihole2 | [✓] TCP (IPv6)
pihole2 |
pihole2 | [i] Pi-hole blocking will be enabled
pihole2 | [i] Enabling blocking
[✓] Pi-hole Enabled |
So, caps still aren't getting set, But FTL is launching anyway so... are things actually working? If you run the 2022.07.1 image, do you still see the same message about failing to set caps, and were things working then?
|
Dev works for me 👍 |
|
Tagged |
|
Yepp, latest :dev seems to run fine :) |
|
thankyou @PromoFaux |
This is a: Bug
Details
2022.08 not starting on Synology NAS, reverting to 2022.07.1 (tag
2022.07) makes it work again.Related Issues
How to reproduce the issue
Console output:
These common fixes didn't work for my issue
docker runexample(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.
2022.7.1 works without issue, above log file shows issues with file/process `/usr/bin/pihole-FTL':
The text was updated successfully, but these errors were encountered: