Container manager image updates, only for docker hub?

[leriak]

With DSM 7.2 and container manager I've moved the containers I managed with docker-compose to "Projects" on Container Manager.
I had not used the Synology Docker app on previous versions, so I'm not sure if the behavior below was already as it is now or not.

On the "image" tab, it shows a note if an image tagged as latest has a newer version available. However this seems to only happen for the images from the base "registry" which I'm assuming is docker hub.

On the screenshot below the fail2ban and jellyfin images from the lscr.io registry had updates but were not showing, and after updating over ssh (docker-compose pull) and recreating the containers the older images who had not been removed did not appear on the list either, so I had to remove them over ssh also (docker image prune -f)

 

[one-eyed-king]

Docker users Docker Hub as default container image registry. Whenever an image repository doesn't specify a registry, then docker.io will be used as registry. Whenever an image repository has no namespace then library will be used. E.g. the repo+tag postgres:latest pulls docker.io/library/postgres:latest under the hood.

I have no idea how the check actually is implemented:

• if they compare it by pulling the manifest for the repo+tag, it should be independent of the registry
• if they use the search api of Docker Hub, then it might explain why it's only working with Docker Hub.

I would suggest opening a support ticket and claim it's a bug

 

[leriak]

It looks like Linuxserver also publishes their images to docker hub, I could just change the image name of the yaml file...

I would suggest opening a support ticket and claim it's a bug

Will do and report back, thanks!

 

[leriak]

I heard back from Synology support, this functionality is not available.
The support rep has filled a feature request form in my name, and "hopes" it will be implemented...
I'm not holding my breath...