Last updated on 31 December 2024
Important or Recent Updates
| History Updates | Date |
|---|---|
| New guide for Container Manager | 25/04/2023 |
The new Container Manager makes updating container images super easy, it can all be done via the UI and no need to SSH into your NAS for updating Docker Compose projects!
Let’s Begin
Head over to the Image tab in Container Manager, in the list of images you will see updates next to the ‘Tag’ field.
You will only be notified of updates for images that you have selected a general tag, such as Latest or Nightly, if you have a specific version number it will remain as is. It is also worth noting that images from GitHub or other sources outside of hub.docker.com will not receive update notices.
Click on the ‘Update available’ button next to the images you want to update, then the screen below will appear, click the Update button.
Then confirm the Update and you will see the image download in the main list.
Container Manager will automatically stop and update your running containers.
Sometimes you may find the container doesn’t get reset correctly with the new image. If this is the case take the extra couple of steps. Stop the container you are updating, then from the top menu click Action > Reset.
Your container will now be running the latest image.
Extra step for Containers part of a Project
If you update a container within a Project it can cause the overall project to fail if that container relies on another. For example updating Gluetun will break the network connection for containers running through it.
Go to the Project tab and select the project you wish to rebuild, then from the Action menu press Stop.
Next click the Action Menu again but this time select build – This will remove the containers and then rebuild them with the updated images.
That’s it, going forward you can easily update containers using this method.
Looking for some help, join our Discord community
If you are struggling with any steps in the guides or looking to branch out into other containers join our Discord community!
Buy me a beverage!
If you have found my site useful please consider pinging me a tip as it helps cover the cost of running things or just lets me stay hydrated. Plus 10% goes to the devs of the apps I do guides for every year.
noob suggestion here again – first time accessing this page of course I have no containers and had a slight freak out – please update and point out the obvious about ADDING containers, or possibly move the ‘updating the containers’ section to after actually adding containers – just to stop noobs from me panicing 🙂 thank you.
Ha, don’t follow the left menu in order, which ever order I put it in someone manages to then ask to move it around again lol 😛
Hey there! Following the steps to upload the QBT/Gluetun container. I stop > build the project but it does not pull an updated image. It just restarts the containers and they remain un-updated. Is there any way to force them to pull the latest version?
If you are pulling the latest image updates it should use them when doing as you mentioned. Are the images set to ‘latest’ in the compose
I have the same issue.
Step 1 – I stopped the project.
Step 2 – I pressed build and the project was rebuilt successfully.
Step 3 – Checked the image section of docker and it was still showing that there was an update available for QBT and Gluetun.
Both QBT and Gluetun are set to “latest” in the compose file. Is there an extra step that I am missing?
Hey – So I believe that Container Manager only refreshes once per day
If you click on the ‘View Tag Versions’ link in the screen that has the Update button, it will take you to Docker Hub so you can see when the last image version was released. – it could have overlapped with CM checking and Docker hub seeing another new version.
If you pull the latest version again does the update notification go away. No steps missing this is the right way to do it.
Hello – Thank you for the quick reply. I tried this method twice yesterday and once again today, still no luck. The project rebuilds but the images continue to show that there are updates available for QBT and Gluetun.
Is there a different method that I can use that won’t break my set up?
Very odd couple of other methods
1) You can manually pull images via SSH (this is what DSM is doing in the background) – Stop the project then login to your Diskstation via SSH – just like the user setup guide. Then use these two commands one at a time to pull the latest images for each.
sudo docker pull qmcgaw/gluetun
sudo docker pull linuxserver/qbittorrent
Then start up the project again and it will use the latest images.
OR
2) Stop the project and then delete the containers within the ‘Containers’ section of Container Manager (Don’t delete any folders!) Then in the Images section of Container Manager again delete the two said images. – At that point you can then go back into the Project and start it back up – it will pull fresh images.
I did the 2) option and it still says there is an update available.
Is it possible that I am running the “latest” and the update is reflecting a beta version that is not considered the “latest” yet?
That’s the only thing that makes sense to me.
I would just ignore the notification at this point as it is not correct or delayed as there was a Gluetun image update last night. Maybe stop and start the whole Container Manager package in case its being weird.
https://hub.docker.com/layers/qmcgaw/gluetun/latest/images/sha256-e0c476e4b793ab41f16e79f85ea2ad74ad6b0546b1d2cf835c59c17eb00f67fe
Last update Dec 27 8:21pm
Hey – So this is actually a Container Manager bug – it’s fixed in the upcoming version (You can upgrade to the Beta)
Man, you really have thought through everything! I just accidentally updated Glutun using Container Manager in Synology DSM, and then I couldn’t get the qbittorrent container started again. Rebuilt the project and everything is working again! Cheers
Came here to say essentially the same thing. Updated Qbittorrent via Container Manager and then was getting a “no such container” error when trying to restart the project. Stopping and rebuilding fixed it. Thanks, great guide.
Love your website, referred to it many many times.
Have you thought about doing the Audiobookshelf setup at all?
I did have this running for a bit.
I will pop on the list, in the meantime grab the compose information from the link below and use something like the Radarr guide as a basis for getting the ‘Project’ in place and folders.
https://paste.drfrankenstein.co.uk/?0f5a25a327137bfd#7GXEkpcLvn1zfsX3vZDusDNJHJiD6jkpaP5ErLP1Tmnh
https://www.audiobookshelf.org/docs#docker-compose-install