docker-pi-hole

docker-pi-hole copied to clipboard

Please note that this issue could be hard to reproduce, feel free to close it if the chance to happen seems too low.

Versions

• Pi-hole version is v5.9
• AdminLTE version is v5.11
• FTL version is v5.14
• Container tag is: 2022.02.1

Platform

• OS and version: Ubuntu 20.04 / AMD64
• Platform: Docker

Expected behavior

From the docker log of Pi-Hole container, there's a section displaying the versions, the latest version expected to be the actual latest version on GitHub:

 ::: Docker start setup complete
  Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
  Pi-hole version is v5.9 (Latest: v5.9)
  AdminLTE version is v5.11 (Latest: v5.11)
  FTL version is v5.14 (Latest: v5.14)
  Container tag is: 2022.02.1

Actual behavior / bug

The strange thing is I saw the latest version older than the current version, when I upgrade Pi-Hole Docker image from 2022.01.1 to 2022.02.1:

 ::: Docker start setup complete
  Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
  Pi-hole version is v5.9 (Latest: v5.8.1)
  AdminLTE version is v5.11 (Latest: v5.10.1)
  FTL version is v5.14 (Latest: v5.13)
  Container tag is: 2022.02.1

Steps to reproduce

I can't reproduce it yet.

Tried to downgrade and upgrade the Pi-Hole in the same host, same environment again, but the problem didn't appear after.

Also tried to upgrade another Pi-Hole docker instance, but the problem didn't happen.

I've noticed this a few times when switching between container tags, but it's never annoyed me enough (yet!) to look into it :)

I think it only happens when volumes are persisted, and the update checker (which I can never remember the trigger of) hasn't fired before the information is output

Yep, just hasn't run the 'latest' check when you first start up a new container.

Hello, same here. I use persisted volumes for Pi Hole in Docker. And the wrong "latest version" problem appears in my constellation whenever I update the Pi Hole Docker.

Same problem here

This is a different problem... (but one that will be fixed in the next version)

Hello, same here. I use persisted volumes for Pi Hole in Docker. And the wrong "latest version" problem appears in my constellation whenever I update the Pi Hole Docker.

Hello, short question. Is there a chance to fix the problem that i have reported?

Maybe, maybe not. It's cosmetic, and usually sorts itself out after a small time, right?

I think I know where to do it, it's just getting around to it. The running of the container should not be affected, so it is lower priority

@PromoFaux correct!

Maybe, maybe not. It's cosmetic, and usually sorts itself out after a small time, right?

Not here. How sorts this itself out after a time? In my installation it shows still the old version (Docker Tag 2021.12) But yes it's cosmetic.

@ogheinz77 , You're seeing something different to that which is reported in the OP, at least I think so.

Please explain exactly which part is showing the old version.

Please also provide a debug log (pihole -t from inside the container) and the output of docker inspect pihole (from outside the container - and if your container is not called pihole, then replace pihole with the name of your container)

@ogheinz77 , You're seeing something different to that which is reported in the OP, at least I think so.

Please explain exactly which part is showing the old version.

Please also provide a debug log (pihole -t from inside the container) and the output of docker inspect pihole (from outside the container - and if your container is not called pihole, then replace pihole with the name of your container)

@PromoFaux, Container is called pihole in Docker. I have send you a e-mail with the docker inspect pihole output. Hope that helps you to find the problem.

What are you using to manage your container? You need to destroy and recreate the container between updates (per the upgrade guide in the readme) else things will start to go wrong. But it is definitely a different issue than that which was reported in the OP

Please stop, delete, then recreate your container - and if you still have the same issue, please reopen a new issue thread for support.

Try to remove the ENV var from your config:

  "PIHOLE_DOCKER_TAG=2021.12",

And recreate your container.

What are you using to manage your container? You need to destroy and recreate the container between updates (per the upgrade guide in the readme) else things will start to go wrong. But it is definitely a different issue than that which was reported in the OP

Please stop, delete, then recreate your container - and if you still have the same issue, please reopen a new issue thread for support.

@PromoFaux, My Pihole runs on a Synology and i am using Synology Docker Manager. When i upgrade Pihole i reset the Container, download the new image and start the Container again. So I don't need to change the settings every time, e.g. Volume and environment settings. When i destroy and recreate the container all these settings are gone, correct?

Follow this: (no experience with using synology docker manager. I have a syno, but I just use docker-compose on the command line, this is from a google search)

https://www.wundertech.net/how-to-update-docker-containers-on-a-synology-nas/

There are also a load of stale environment variables in your setup from where you've updated incorrectly in the past. Remove the following from your configuration before starting the new container:

PIHOLE_DOCKER_TAG
CORE_VERSION
WEB_VERSION
FTL_VERSION
PIHOLE_VERSION
PIHOLE_ARCH
PIHOLE_TAG

Follow that guide above. Also see here for notes on upgrading : https://github.com/pi-hole/docker-pi-hole#upgrading--reconfiguring

I'm going to ask that you stop replying on this thread about your issue - as it is unrelated to the OP's issue (third time of me mentioning). If you are still having trouble, please open a new issue thread

This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.

Still needs a fix though.

This Issue is fixed for my understanding by Release 2022.09 - so this issue should be closed… @yubiuser

From my docker logs pihole:

  Current Pi-hole version is v5.12
  Current AdminLTE version is v5.14
  Current FTL version is v5.17
  Container tag is: 2022.09