Prevent breakage on todays PiHole image update

[one-eyed-king]

In todays update of the pihole/pihole:latest image, two environment variables - shipped with the image - have been changed.

Typicaly no one touches those environment variables when creating a container. Though due to the behavior of Portainer and the Docker UI reset function, all parameters of the existing container will be reused when creating a new container. Thus, the changed variables shipped with the new image, get replaced by the values of the old container.

If you experience this problem, simply remove these two environment variables after the failed update (or before resetting the container to create a container based on the new image):
- PIHOLE_INSTALL
- VERSION

or update their values:
PIHOLE_INSTALL=/etc/.pihole/automated install/basic-install.sh
VERSION=v5.8.1

The space character in automated install is not a typo

 

[Telos]

Though due to the behavior of Portainer and the Docker UI reset function, all parameters of the existing container will be reused when creating a new container.

I trust this would not occur using docker-compose, unless your yml file contained over-riding environmental values. Is that correct?

 

[one-eyed-king]

Correct