Ale tam jest podany przykład Portainera i jego ręcznej aktualizacji. Więc nie musisz ale Portainer lepiej się sprawuje od domyślnej aplikacji do contenerów od qnapa. Tu chodziło mi o watchtower.
A mi wyskoczylo cos takiego przy probie zalogowania sie do www pihol'a ???
Instalowalem PiHole na ContainerStation 3.0.0.122 tak wiec troche inaczej niz na filmie bo tam byl starszy (chyba 2.6) ale niby proces sie udal wedlug CS proces dziala ale przy prubie zalogowania sie wyswietla sie to:
dodanie admina zadzialalo ale dziwne bo nie wola hasla a jestem zalogowany moge dodac listy ale i tak pihole nie dziala
wypisuje cos takiego:
There was a problem applying your settings.
Debugging information:
PHP error (2): parse_ini_file(/etc/pihole/setupVars.conf): failed to open stream: Permission denied in /var/www/html/admin/settings.php:17
Wywalilem wszystko i zainstalowalem jeszcze raz. Teraz niby nie ma tego bledu (PHP error (2): parse_ini_file(/etc/pihole/setupVars.conf): failed to open stream: Permission denied in /var/www/html/admin/settings.php:17) - za to jest inny: Stopping pihole-FTL
Zrobilem tak jak w filmie (z poczatku watku)- co prawda troche dodtosywanym do Contener Station 3 (bo w CS 2.x jest troche inaczej polozenie niektorych tych funkcji).
Moge porobic zrzuty ekranu czy cos (terminal?) - tylko czego potrzeba do diagnozy?
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service cron: starting
s6-rc: info: service cron successfully started
s6-rc: info: service _uid-gid-changer: starting
s6-rc: info: service _uid-gid-changer successfully started
s6-rc: info: service _startup: starting Starting docker specific checks & setup for docker pihole/pihole Setting capabilities on pihole-FTL where possible Applying the following caps to pihole-FTL:
* CAP_CHOWN
* CAP_NET_BIND_SERVICE
* CAP_NET_RAW Ensuring basic configuration by re-running select functions from basic-install.sh
Installing configs from /etc/.pihole... 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
[✓] Installing latest logrotate script Creating empty /etc/pihole/setupVars.conf file. Assigning random password: n1VEm9IZ
[✓] New password set Added ENV to php:
"TZ" => "Europe/London",
"PIHOLE_DOCKER_TAG" => "",
"PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log",
"CORS_HOSTS" => "",
"VIRTUAL_HOST" => "ac840eefabaa", Using IPv4 and IPv6 setup_blocklists now setting default blocklists up: TIP: Use a docker volume for /etc/pihole/adlists.list if you want to customize for first boot Blocklists (/etc/pihole/adlists.list) now set to: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts Converting DNS1 to PIHOLE_DNS_ Converting DNS2 to PIHOLE_DNS_ Setting DNS servers based on PIHOLE_DNS_ variable Applying pihole-FTL.conf setting LOCAL_IPV4=0.0.0.0 FTL binding to default interface: eth0 Enabling Query Logging Testing lighttpd config: Syntax OK All config checks passed, cleared for startup ... Docker start setup complete
pihole-FTL (no-daemon) will be started as pihole
s6-rc: info: service _startup successfully started
s6-rc: info: service pihole-FTL: starting
s6-rc: info: service pihole-FTL successfully started
s6-rc: info: service lighttpd: starting
s6-rc: info: service lighttpd successfully started
s6-rc: info: service _postFTL: starting
s6-rc: info: service _postFTL successfully started
s6-rc: info: service legacy-services: starting
Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
s6-rc: info: service legacy-services successfully started Creating new gravity database Migrating content of /etc/pihole/adlists.list into new database
[✗] DNS resolution is currently unavailable
[✓] DNS resolution is now available
Neutrino emissions detected...
[✓] Pulling blocklist source list into range
[✓] Preparing new gravity database Using libz compression
[✓] Creating new gravity databases
[✓] Storing downloaded domains in new gravity database
[✓] Building tree
[✓] Swapping databases
[✓] The old database remains available. Number of gravity domains: 177888 (177888 unique domains) Number of exact blacklisted domains: 0 Number of regex blacklist filters: 0 Number of exact whitelisted domains: 0 Number of regex whitelist filters: 0
[✓] Flushing DNS cache
[✓] Cleaning up stray matter
[✓] FTL is listening on port 53
[✓] UDP (IPv4)
[✓] TCP (IPv4)
[✓] UDP (IPv6)
[✓] TCP (IPv6)
Pi-hole blocking will be enabled Enabling blocking
[✓] Reloading DNS lists
[✓] Pi-hole Enabled
Pi-hole version is v5.15.3 (Latest: v5.15.3)
AdminLTE version is v5.18.3 (Latest: v5.18.3)
FTL version is v5.20.1 (Latest: v5.20.1)
Container tag is: 2023.01.10
Niby tak ale jak byly reklamy na TV tak sa, a lapek za cholere nie chce sie z nim polaczyc chcoc mam wywalone inne dnsy z niego niz pihole
192.168.1.177 - TV
192.168.1.11 - Lapciok