I use docker compose to deploy my containers,so unraid's buildin container update function dosen't work my containers.

And I already disabled 'Docker update notification' as below

Edited July 7, 20233 yr by nukecat

On 7/7/2023 at 9:40 PM, MAM59 said:

the very simple trick is: NOT TO USE ":LATEST" for the docker container's version.

Pick one version, add it to the string and you are done!

like:

 

Here 2.9.22 is the version I like (all newer give me troubles). So with this "source" setting it will never look for newer versions and never bother me with updates for this docker.

 

Thx,But some container still need to user latest tag

3 minutes ago, MAM59 said:

never heard of this before?!?!? can you give me an example?

 

sorry for my english.

i mean i need to keep some service(container) up to date and have to use 「latest」 tag.

 

1 hour ago, MAM59 said:

English is not my natural language too :-)))

 

I did not tell you that you cannot use the :latest tag for any container, I just meant it for NPM. The tag can be set for any container differently, it just defaults to :latest, but this is only for convinience.

You should only modify the tag for the nginx container. (in the mean time they claim, they have fixed it, but it needs a total rework of every configured proxy host. So I will stay with 2.9.22)

 

Im a software developer,I know I can use stable tag instead of  THE DEFAULT LATEST TAG to avoid upgrade check.

I chose to use the latest tag on purpose（not on all service/containers,just some of them）, to keep the service up to date , and let watchtower upgrade those containers for me quietly.

Just want to know if there is a way to disable unraid's container upgrade check which in my case , is unusable since I use docker compose instead of unraid's templates.

When using docker compose in unraid , the update button dosent work ,it just simply fail during process.Therefore the 「⚡️ update ready」hint is useless and annoying.And even if I manually upgrade by 「docker compose pull && docker compose up -d」or  watchtower already upgrade those  「update ready」containers , the 「⚡️ update ready」sign wouldnt disappear!

Please dont argue with me about what tag I should use anymore.

 

------------------------------------------------------------

 

我是一名程序员，说不上精通，但是平常经常使用docker，我也知道默认情况下docker会使用latest作为镜像的tag。

我是特意使用latest作为tag的，因为我需要一部分服务永远保持最新，为此我也部署了watchtower来静默更新容器。

我只是想知道有没有办法屏蔽unraid的容器更新检查。

我在unraid里安装了docker compose 插件（我工作中还有以前使用其他系统的时候，我更习惯用docker compose ），在unraid中使用docker compose来部署的容器，虽然在webui中能够提示容器更新，但是点击更新按钮会报错，容器也不会被正确更新，所以「⚡️ update ready」这个提示对我来说并没有用处，毫无意义还多少有点碍眼。

Edited July 19, 20232 yr by nukecat

If you are using docker compose there is no way currently to disable the update ready text.

Until yesterday i was on 6.11 and i did not had this problem. Maybe i installed a plugin that hide the checks. Now it has this fake "update ready" warning which is not true. There's a way to change or remove the internal status? This version check should be saved somewhere. For example i could run a script that deletes the updates status every 10 seconds. Or write "installed version 999.999999" somewhere which will be the latest.

 

Where is this "update ready" info stored? So i can delete it automatically

 

edit: the info is stored in

 

/mnt/user/system/docker/unraid-update-status.json

 

and it's populated by the command

 

/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate check

which is run every monday

 

for example it contains:

 

    "library/mariadb:latest": {
        "local": "sha256:9ff479f244cc596aed9794d035a9f352662f2caed933238c533024df64569853",
        "remote": "sha256:5d851e999b84625ef9810589e832686cae58453452698ee69e2980041e626eb2",
        "status": "false"
    },

 

I was able to change the status of caddy to "up-to-date" by changing to

 

    "library/caddy:latest": {
        "local": "sha256:b3a7eac3daba82e1d682a7fa3f11b6d0dbe32869cdcc835fd30748021fbe3b9f",
        "remote": "sha256:b3a7eac3daba82e1d682a7fa3f11b6d0dbe32869cdcc835fd30748021fbe3b9f",
        "status": "true"
    },

 

unfortunately, deleting the file has no effect, maybe is cached somewhere else

 

I also tried to make an invalid entry which on the GUI results as "not available"

 

    "library/munin-munin:latest": {
        "local": null,
        "remote": null,
        "status": "undef"
    },

 

but it has no effect

 

i need to find a way to automate this otherwise my OCD will drive me crazy seeing "update ready" instead of "up-to-date". I exclusively use the docker compose plugin and never use docker containers from the community apps

Edited September 16, 20232 yr by PixelPrint
found more info

Solution:

 

after manually updating the containers, run this:

 

rm /mnt/user/system/docker/unraid-update-status.json
/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate check

 

the first command will remove any status of updates, the second line will check for updates, recreate that json file, then tell the status of the containers to the GUI

 

Actually, i created for myself a more complex script that will update everything, then remove that json file.

 

it's something like this

 

percorso="/mnt/user/docker/"
finale="/docker-compose.yml"
comando="docker compose -f"
managerpath="/boot/config/plugins/compose.manager/projects/"
override="/docker-compose.override.yml"

function aggiornamatic() {
        #primo argomento: nome directory
        percorsocompleto=$percorso$1$finale
        $comando $percorsocompleto -f $managerpath$1$override build && $comando $percorsocompleto -f $managerpath$1$override pull && $comando $percorsocompleto -f $managerpath$1$override down && $comando $percorsocompleto -f $managerpath$1$override up -d
}

#aggiornamatic: primo parametro è il nome container
aggiornamatic "afterlogic"
aggiornamatic "borgmatic"
aggiornamatic "caddy"
aggiornamatic "cloudflared"
docker image prune --all
rm /mnt/user/system/docker/unraid-update-status.json
/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate check

 

On 9/16/2023 at 11:45 PM, PixelPrint said:

Solution:

 

after manually updating the containers, run this:

 

rm /mnt/user/system/docker/unraid-update-status.json
/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate check

 

the first command will remove any status of updates, the second line will check for updates, recreate that json file, then tell the status of the containers to the GUI

 

Actually, i created for myself a more complex script that will update everything, then remove that json file.

 

it's something like this

 

percorso="/mnt/user/docker/"
finale="/docker-compose.yml"
comando="docker compose -f"
managerpath="/boot/config/plugins/compose.manager/projects/"
override="/docker-compose.override.yml"

function aggiornamatic() {
        #primo argomento: nome directory
        percorsocompleto=$percorso$1$finale
        $comando $percorsocompleto -f $managerpath$1$override build && $comando $percorsocompleto -f $managerpath$1$override pull && $comando $percorsocompleto -f $managerpath$1$override down && $comando $percorsocompleto -f $managerpath$1$override up -d
}

#aggiornamatic: primo parametro è il nome container
aggiornamatic "afterlogic"
aggiornamatic "borgmatic"
aggiornamatic "caddy"
aggiornamatic "cloudflared"
docker image prune --all
rm /mnt/user/system/docker/unraid-update-status.json
/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate check

 

How should this script be used? Can you talk about it in detail? Thank you.

I run it manually on sunday afternoons, as i like to watch what the updates do. In this way at midnight when unraid checks updates, finds nothing.

 

Additionally, i hide the "update column" using a browser extension called "Amino", which allows to add custom CSS rules to pages.

 

I added this custom CSS rule for the server page:

 

.updatecolumn {
    display: none;
}

 

On 9/16/2023 at 5:45 PM, PixelPrint said:

Solution:

 

after manually updating the containers, run this:

 

rm /mnt/user/system/docker/unraid-update-status.json
/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate check

 

the first command will remove any status of updates, the second line will check for updates, recreate that json file, then tell the status of the containers to the GUI

 

Actually, i created for myself a more complex script that will update everything, then remove that json file.

 

it's something like this

 

percorso="/mnt/user/docker/"
finale="/docker-compose.yml"
comando="docker compose -f"
managerpath="/boot/config/plugins/compose.manager/projects/"
override="/docker-compose.override.yml"

function aggiornamatic() {
        #primo argomento: nome directory
        percorsocompleto=$percorso$1$finale
        $comando $percorsocompleto -f $managerpath$1$override build && $comando $percorsocompleto -f $managerpath$1$override pull && $comando $percorsocompleto -f $managerpath$1$override down && $comando $percorsocompleto -f $managerpath$1$override up -d
}

#aggiornamatic: primo parametro è il nome container
aggiornamatic "afterlogic"
aggiornamatic "borgmatic"
aggiornamatic "caddy"
aggiornamatic "cloudflared"
docker image prune --all
rm /mnt/user/system/docker/unraid-update-status.json
/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate check

 

This used to work for me but stopped working out of nowhere with unRAID 7 (I guess).

 

The command 

/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate check

takes forever and does nothing anymore...