- Annoyance
I'm using a couple of Docker containers with docker-compose on my system.
One of the stacks is for my web-services (nginx, nextcloud, wordpress) but the exact containers don't really matter.
I use docker-compose though a docker-container (docker/compose:latest).
The problem I have is, that the "Check for Updates" in the Unraid WebUI only works once for those containers.
After creation it'll show "up-to-date" just fine, but after detecting an update once, it'll never change, even if the container is updated though docker-compose. The check for updates routine should properly check for updates, even for those containers.
To reproduce:
- Simply setup a stack via docker-compose. I use this alias to invoke the compose container (so compose works just like it normally would though the CLI):
alias docker-compose='docker run --rm \
-v /var/run/docker.sock:/var/run/docker.sock \
-v "$PWD:$PWD" \
-w="$PWD" \
docker/compose:latest'
- Press "Check for Updates" in the Docker section of the unraid WebUI, it'll show "up-to-date"
- Wait for an update on one of the containers in the stack.
- Check for Updates in the WebUI again, it'll show "apply update"
- Update the container via compose (docker-compose pull, (docker-compose down), docker-compose up -d)
- Check for Updates in the WebUI again, it'll still show "apply update" even if the container should show up-to-date.
The Portainer instance I've running correctly shows the container being on the correct image (latest, stable, etc.), just Unraid still "thinks" that there is a update available.
My installed Plugins (even if I think that they are completely unrelated):
-
Community Applications
-
Dynamix Cache Directories
-
Dynamix File Integrity
-
Unassigned Devices
-
Unassigned Devices Plus
-
Unraid Nvidia
The system is running on a X370-Pro, Ryzen 1700X, 32GB ECC RAM @ 2666MHz, GTX 1650 LP, 400W SeaSonic PSU and a bunch of drives.