- Minor
Hi,
I'm managing docker with Portainer (because I prefer compose files) and container updates with watchtower. This works perfectly. I do still use the Unraid interface by specifying net.unraid.docker.icon and net.unraid.docker.webui. Beautiful.
If Unraid detects a possible update for a container I get a notification. All good, for all containers. Actually updating containers from Uraid for my containers made with Portainer does not work ending in a "Configuration not found." error. This is expected of course, as Unraid has no configuration for said container. However, if I update the said container with Watchtower something strange happens. The container updates, but Unraid keeps signalling that there is an update available, even though this is no longer the case. Manually running "Check updates" from Unraid does not seem to solve this. Recreating the container also does not work. Unraid just keeps saying there is an update even though there is no longer the case. The only way to solve this is by deleting /var/lib/docker/unraid-update-status.json forcing a reset. This seems to be a regression from and earlier fixed bug: https://forums.unraid.net/topic/93399-683-custom-docker-stuck-on-apply-update/.
It seems Unraid is once again only checking for newly available updates and not checking for containers that are no longer out of date. Should be an easy fix for some conditional?
Hope this bug report helps,
Kind regards,
Jori Huisman
-
2
