Install the app
How to install the app on iOS

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature may not be available in some browsers.

Docker tag?

Cyberwasp

Subscriber
386
71
NAS
Synology DS920+
Operating system
  1. Windows
Mobile operating system
  1. Android
Today I opened Pihole and at the bottom of the page it says there is a "Docker Tag update." Haven't seen this before and was wondering how to fix it. TIA
 
Last edited:
Since no one is responding, I am giving it a shot.

I don't know whether this message means that a new image is pushed for either a new or an existing tag.
Back then, when I was still using Pihole, I know that they add environment variables to their images, that are image specific, and end up in the created container.

If you pull the updated image with the Container Manager, and reset the container, the old container configuration will be applied to the new container. Watchtower and Portainer will do the same. This behavior usually works great with most images, but can cause problems with the Pihole image (I remember that it did a couple of times in the past).

Though, if you use docker compose for updates, there won't be a problem, as it will always remove the old container and create a new container using the configuration you configured in the compose file.

The question is: what are you using to manage your containers?
 
I used Compose to initially set it up. Since then, when an update is released, I stop the container in manager and click on update. Then start it up. I tried that but it said there is no update. It's still working so I'll wait and see if an update arrives. Just seemed odd. Just wanted to check with the experts here.
 
The easiest way to update the "same tag new image scenario" is on the shell using docker compose pull, followed by a docker compose up -d. If there is in fact a new tag, then modifying the image's tag, followed by docker compose up -d should do the trick.
 
For the heck of it, I just checked again in docker container, and it announced an update was available. I guess Pihole was tired of waiting and started to complain to me. Once updated the tag update vanished. Now if I remember next time. Thank everyone!!
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Popular tags from this forum

Similar threads

There must be already be some sort of dependency, as the deluge service joins the network namespace of the...
Replies
6
Views
674
Ok got this running.. But how do I specify the custom_user/password settings in the yaml-file? EDIT...
Replies
7
Views
961
  • Question Question
Do realize, that enabling any user to run docker containers is largely the same as giving that user full...
Replies
6
Views
1,742
Hello, I already have it configured perfectly with wireguard. I was looking at the Gluetun configuration...
Replies
4
Views
1,679
Thanks... I tried something similar with rsync. The docker volume lived in...
Replies
7
Views
1,890
I can’t find any option to restore just the settings. 1710356648 Phew, managed to fix it. Within the...
Replies
4
Views
1,321

Thread Tags

Tags Tags
docker

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending content in this forum

Back
Top