I'm using the Compose.Manager plugin so I can use docker compose stacks instead of individual docker containers as this was how my server was set up prior to migrating to unraid.

 

I am able to update the stack using the 'Update Stack' button, but the Docker tab still says there are updates available to most of my docker containers.

 

If I click 'apply update' on a container, it breaks the stack and that container no longer functions properly (I suspect because it's performing the update outside of the stack).

 

While this isn't a big deal, it is slightly annoying that I get pinged every day for updates that I can't apply.

 

It seems like Compose.Manager and the standard Docker plugin pull updates from different sources. Am I correct in thinking that? Is there any way to either disable the update check for containers in the stack, or to tell the Docker plugin to look at the Compose file for updates?

 

cherry-diagnostics-20231209-0759.zip

Here is my compose file (with some sensitive info redacted)

docker-compose.yml

Edited December 9, 20232 yr by count-zero

On 12/9/2023 at 8:00 AM, count-zero said:

It seems like Compose.Manager and the standard Docker plugin pull updates from different sources. Am I correct in thinking that? 

No, the Dockerman system has its own method of storing the current and latest available version of docker images. Compose.Manager does not integrate with Dockerman in this respect (in fact it does no update tracking of its own it just provides a button with runs a stack update command). 

 

On 12/9/2023 at 8:00 AM, count-zero said:

 Is there any way to either disable the update check for containers in the stack, or to tell the Docker plugin to look at the Compose file for updates?

No, at the moment there is no good way to remove the "Update Available" link.

 

On 12/9/2023 at 8:00 AM, count-zero said:

While this isn't a big deal, it is slightly annoying that I get pinged every day for updates that I can't apply.

The pings are from the Fix Common Problems plugin correct? Best to just disable the update check in FCP.

Gotcha, thanks for the info.

 

I've disabled the update check in FCP and will just come in to check manually from now on.

 

Thanks again!

At least using a docker folder (here /mnt/user/docker, as I have a dedicated share for it), you can do this:

 

# This is my folder. Change it to what yours is. Also, if using an image instead, need to find out how to mount it.
DOCKER_FOLDER="/mnt/user/docker"

# Remove the current update status files and back it up just in case
mv "${DOCKER_FOLDER}/unraid-update-status.json" "${DOCKER_FOLDER}/unraid-update-status.json.bkp"

Then just re-run the update checks. It'll compare all your containers with upstream again and it should work.

You can also just manually edit the file to find the right entry, make both hashes equal and change the setting.

Man I wish this bug would get fixed.  End of 2024 and there is still no way to disable update checks on individual dockers which were made using the manual docker compose option.  Could this be a fix for Unraid 7 maybe?  Drives me crazy seeing these updates available all the time and then having to go through and update 1 by 1 as to not accidentally "update" the docker compose dockers.

I feel exactly the same way!
Have you found a solution yet?

26 minutes ago, madmaxx89 said:

I feel exactly the same way!
Have you found a solution yet?

Try 7.0.0

The behavior is exactly the same in 7.0.0. Still the same issue. Not critical but indeed annoying.

 

EDIT: I just noticed that with 7.0.1 things have changed and there is no longer a message saying tha there are updates available on containers created manually or via compose.

Edited March 7, 20251 yr by googleg