How to Update a Docker Container on a Synology NAS!
HTML-код
- Опубликовано: 6 янв 2021
- This tutorial will show how you can update Docker Containers on a Synology NAS using Synology's GUI or Docker Compose!
✅ Written Instructions: www.wundertech.net/how-to-upd...
🔔 Subscribe for more tech related tutorials and overviews: link.wundertech.net/ssYt
🚀 Product Recommendations: link.wundertech.net/rmYt
❤️ Check out our website: link.wundertech.net/wtYt DISCLAIMER: The information in this video has been self-taught through years of technical tinkering. While we do our best to provide accurate, useful information, we make no guarantee that our viewers will achieve the same level of success. WunderTech does not assume liability nor responsibility to any person or entity with respect to damage caused directly or indirectly from its content or associated media. Use at your own risk.
WunderTech is a trade name of WunderTech, LLC. 
Наука
You made this so simple! Love it, thanks!
Thanks so much. Very well done explainer. It's so much more comfortable to have a backup container while you check the update.
Excellent guide. Sorted me out so quickly. Thank you for taking the time to make this video.
Short and informative technical clip. Thank you!👍
Just ran into my first sonarr update and this video helped me perfectly. Appreciate it!
Thank you! Very well shown and explained.
Thanks for the explanation, I was doing it by downloading the image and then re-creating the container but it felt so cumbersome! Glad there is an easier way as soon as I heard your explanation it clicked.
Excellent vid just wat i needed thank you
This was a nice, clean and easy way to update my Plex server. Thanks!
thank you for sharing this!
Very helpful, thank you!
How is your channel so lowkey?? You make the best, quick/straight to the point , clearly spoken, well laid out and quality videos!! In the past couple of weeks I've utilized several of your videos to get me "unstuck". I need somewhere to donate!
Thanks a lot, I appreciate the kind words! No worries on the donation, watching is more than enough. I appreciate the thought though!
Used this to update pihole. Easy and straightforward, unlike the documentation which tells you to use commands of which I have no idea where to put them. I'm spending a lot of time learning anything about my NAS but I don't have time for everything! :p
Great tutorial, thanks :)
Thank you. great video.
Exactly what I was after as I have no clue how to SSH! Thank You!
Thank you! =D Always had to recreate the container. Subbed.
Thank you! Glad that it helped!
Thank YOU!!!
Oh man! /o\
And i thought being on "latest" would update itself automatically. 😆
Thank you!
One thing you need to remember when using the 'Duplicate Settings' option in Synology GUI is that it will not duplicate local port values if it's other than auto, for obvious reasons.
Great input! Thank you for sharing!
Glad i read this, was waiting for the container to come back up but nothing, checked port values and that was my issue. Great tip.
Thank you - spot on advice for my problem
Thanks for the tip I think this will fix my issue I am having with the videos method on my container with custom ports.
Excellent video. Should get more views.
Thank you so much! Glad it helped!
8 months later & I'm back - Had to search how to do this again haha - Thanks again. Dang Pi-hole
Another tip: If you have Enable Auto-Start turned on, when you duplicate and rename to add "-BACKUP", uncheck that setting so if your server does restart, you don't have two conflicting containers running!
Would you please create a video on your top 10 or so docker containers you use and how those help you ? Thanks a lot, pretty under rated this channel is.
I will definitely create a tutorial for this in the future! Thanks for the kind words!
@@WunderTechTutorials thanks, will wait impatiently. 😄
Thanks!
Thank you so much!!
Awesome tutorials! You deserve more subscribers, maybe add hashtags in description and stuff?
Thanks so much! I can definitely try that! The channel is slowly growing, but I truly appreciate the support!
I wish this process work with OMADA but I have to recreate all the configuration then restore from backup. Ill try your other settings
I followed the first half of the video using the Docker app in Synology to rename and duplicate. The problem I ran in to is that because I assign the Local Port for my containers, when the original is duplicated, it changes Local Port to Auto. I used to just download the latest, stop, clear, and start, but I like the idea of having a backup like you mention. Just need to change the ports between the original and duplicate using your method. Thank you for the video.
If the "clear" method works for you, feel free to keep using it! For whatever reason, I cannot get that to work at all. As soon as I clear the container, it's wipes it out and I need to start over. Wondering if there is a difference between NAS devices, but use whatever you feel most comfortable with!
@@WunderTechTutorials Why does you response feel very aggressive, like you were taking offence to my comment? I was just giving feedback on what I encountered.
@@Ryououki In absolutely no way was that meant to be aggressive. I'm sorry if it came across that way. I was just highlighting that I can't personally get that working, but I know a lot of people can and it's significantly easier (since you just clear the container and it works).
Your feedback is appreciated and I certainly didn't mean to come off aggressively. So once again, I apologize if it came across that way.
@@WunderTechTutorials My apologies for interpreting your previous response incorrectly. I do want you to know I do appreciate your video as I will be using your steps in the future just with the addition of adding the local port change steps. Thanks again.
Thanks for the great explanation! Everything works except the part at 1:50 where you open the URL of jellyfin. If I do that in exactly the order described in your video, jellyfin starts a brand new setup via web assistant. Why? Can you help me with that?
You will first have to mount the config location in the old container:
1. Create a folder in the docker folder on your NAS named "jellyfin", then stop the container. Create a new volume pointed to that folder you just created and use the container path "/config". I left this part out in the tutorial because I stupidly assumed that people would only care about their media data.
2. Start the container, access the jellyfin folder on your NAS and confirm there is data inside of it. If there is, move on to step 3. If not, something isn't mapped properly.
Wouldnt renaming it to backup and than using the new one (that uses the same exact settings) overwrite the files in /config (or what have you) when you start the new container? so the backup container doesnt have its original /config files anymore?
No, it should read the folder and all contents that exist in the folder. It only creates them the data doesn't exist.
Any advice on how to switch tags and update (replace)? I mistakenly setup sonarr using the wrong tag awhile back and now need to switch to :latest instead of :preview
Unfortunately, I think you'd have to recreate the container at that point. However, you can simply map the volumes to where they're currently stored (on your NAS), and all the data should still exist as it always has.
finally figured it out, export the settings from the existing tag (preview), open JSON file and edit that tag to :latest, save. Go back over to registry and download the new container (latest). Click on existing install and import settings, change name to different. Fix port settings and good to go
For my currently running Docker instances, where do I see the version of the image being used?
So I know when I can replace the image.
Sadly (off the top of my head), Synology doesn't give you a great location to check the current version. Can you open the applications that are running in Docker and check their version?
Hello, thank you for the video. I started the new container about 15 min ago and my library is slowly populating on Jellyfin. It does look like my previous metadata is gone however. Any idea how I can retrieve that?
Unfortunately, no way to retrieve if the container has already been rewritten.
@@WunderTechTutorials damn, oh well. Any idea how I can preserve it through future updates?
@@LOLcanIwenLots If you map the /config folder path (shown in the tutorial below), it'll preserve the configuration:
www.wundertech.net/how-to-set-up-jellyfin-on-a-synology-nas/
Faster way to pull all the updates down via the shell:
sudo docker inspect --format {{.Config.Image}} $(sudo docker ps -a --format {{.ID}}) | sudo xargs -n1 -I docker pull {}
(remove the sudo statements if putting in a script, and run script as appropriate user, aka, sudo if needed)
Not a docker Ninja, so there may be an even more streamlined way to pull the latest of all the installed docker images. Once the images are migrated, purge the unused images from cache:
docker image prune
Hey can you help, my old version ist 5.1 not "latest" wen I make copy of the container, he copy also the connection to 5.1 and not to the latest image. Thx
I think for specific versioned containers, you will have to create a new one unfortunately. This is easier to manage when using Docker outside of Synology's GUI.
When I copy settings of older image the port number changes and doesnt copy. When I manually use original port, an error shows it being used. Even when the container is off. Is there a way around this? I have to delete the backup for it to use same container
If you stop and edit the old container, change the ports, then recreate it, you should be good.
how do you check the version of the container that's running?
Generally, you'll have to check the version on the user-interface of the tool you're using.
thank you. lets say i want to delete the backup, how?
Are you talking about after creating the new one? You can safely go through and delete the old container if the new one is running properly.
Is there a way to contact you. I recently ran into a problem with Pihole start/stopping continuously. It started after my provider hooked up a new modem and router. in Piholes logs I noticed this: "Testing pihole-FTL DNS: sudo: unable to resolve host pihole-pihole1: Temporary failure in name resolution." Any idea for a fix other than starting over?
By any chance, did you install the latest container? People are having issues with the latest Pi-hole container. Can you try using an older version and see if it works?
@@WunderTechTutorials I'll try, but right now the registry is not loading! Waiting for Amazon to deliver new router. Cable co issues:)
I finally got everything straightened out and everything is back to normal. I had to whitelist amazon with the new update as all of my Alexa's were complaining! Please keep these tutorials coming, as they are great!
@@cyberwasp461 Glad you got it working!
I duplicated the setttings on teh container and renamed them backup. I messed things up from there. I proceeded to get the newer images in teh registry. The settings did not get switched to the new updated container. I now have 2 containers in my container list. The backup onee continues to allow me to access its gui but the updated version is unsuccessful even after I updated the ports to match those of the old. It is as if I am opening the containers for the first time when I go to open them. I also am getting error messages when i try to run docker-compose up and docker image prune.
Did you have any custom ports by any chance? Can you look at both containers back to back and see what the difference is?
@@WunderTechTutorials one of them may have been changed and i have one that was set with the default.. I ended up starting fresh and deleting the new containers. I then reapplied the ports to the originals titled "backup". Lastly I did ssh for a docker compose pull and it appeared to run successfully. HOWEVER, some of the constainters are not updating and are still asaying that they are out of date. I dont know why. any ideas?
When I start the container back up it still uses the older version. Now I'm not using :latest. It's for Ombi. And the error, when I try to delete the old image, says its because its dependent on it.
Did you double-click on the image from the registry to make sure you downloaded the newest one? Also, are you sure there's a new version?
You will not be able to delete an image without removing the containers that use it. However, your goal should be to download the newest version, duplicate the settings and then delete the old container when you know it works.
@@WunderTechTutorials Yeah I got it to work. I had to delete the container and the image, then create the new image in the location of the old one. I thought doing that would rewrite the folder but it didn't lol
To note though: the method you are showing only works if the image has the same name like :latest or :preview
@@olafcreed4726 That is correct! Glad to hear you got it working!
Is there something that can notify me when there's an update?
Unfortunately, not that I'm aware of 😞
Made a mistake at the 1:10 mark and renamed things incorrectly. Accidentally deleted the original Container and the copy will not work. Any suggestions on finding and restoring the deleted Container on my Synology NAS? It's not in the recycle bin.
Unfortunately, no way to restore it. You'll have to recreate it and point it back to whatever volumes exist. The data is still there, but the container is gone.
Hey - followed the first part of the tutorial with my PiHole docker container and it constantly restarts. It is acting as a DNS server. All help appreciated!
When you say that it constantly restarts, is that on the new container? Anything being written to the log?
@@WunderTechTutorials It will roughly run for 1min, then fall over. Happy to share the log
@@Th3Dean That would probably be best. If it's running for a minute, it could be a more unique type of issue as restarts generally happen immediately.
@@WunderTechTutorials After testing, it is restarting immediately. I've emailed the logs over as I wasn't sure if they would contain any sensitive data 🙏
I followed this first half by duplicating the setting but when I start the new container Jellyfin wants to setup a new server.
Help - whats the fix ?
Do you have a config mount path? I should have included that in my initial instructions, but I made the assumption that most people only cared about the media and that's my fault.
If you go into the old container, create a folder under the "Docker" folder named "jellyfin", then a folder inside of there named "config". Select that folder in the mount path, then map it to the "/config" location. Start the container, stop it, then mount the same path on the new container. All of your info should now be there.
Sorry I’m unaware where Jellyfin got mounted. Ideally I’d like it under the docker folder with the others but it seems to be mounted in an unknown area, otherwise the previous instructions you’ve just sent would seem easy to follow. Any tips for seeing/moving folders outside of all the shares in a GUI so I can relocate it to the docker folder ?
@@jungleboyfromoz If we take a step back, do you still have the old container? If you do and you try and edit it, can you add new mount points? That will allow you to mount the folder anywhere you'd like.
@@WunderTechTutorials yes I still have it. Inside volume I have the movie folders listed only but I don’t think this is what you’re referring too. Is it inside the environment tab? What needs to be edited ?
i try to use this also , but it does not work . by duplicate settings , it will duplicate the settings but also duplicate the container(not updating it to the latest downloaded image)
I had downloaded the latest version of the container, but how to start that one with the settings of what i had in previous version
Or is there a name issue? should the TAG name be 100% the same? Like "jacobalberty/unifi:latest" and not with a version number like "jacobalberty/unifi:v6.5.55"
Because the version number in TAG name will be updated evertytime
Did you download the latest image first? The tag name can be the same (meaning latest is fine), but you still need to double-click the image to download the latest.
@@WunderTechTutorials yes i did download the latest image first. But normally you have to start it, to run it. By duplicate settings of container which has just stopped, it duplicates the setting but also the container itself. It does not use the latest image which i downloaded.
By duplicate settings the TAG name is also duplicate
@@EasyRun74 Is there any way you can check a version number to ensure it's not updating the container?
@@WunderTechTutorials yes by access the site i can see its version of the container program
But i found something else
Go to Registry and download new image (mostly the “latest” version)
Go to Container, select the container you need to update and stop it
From Actions menu select “Clear”
Edit: Under DSM7, the “Clear” command has been renamed “Reset”.
Start the container again
Im using dsm7, so i will try the "Reset" function
@@EasyRun74 My reason for creating this video was because that process did NOT work for me. However, it DOES work for a lot of people and I'm not entirely sure why it won't work for me. It just deletes all of my settings and I need to setup the container from scratch, but if it works, that's great!
I just used this video to upgrade Jellyfin and now I have a new instance of Jellyfin :( I did "duplicate settings". Not sure what I did wrong.
You still have the old container, right? If you start it, is it working properly?
@@WunderTechTutorials yes it still works, but every time I try to duplicate the settings, it doesn't seem to do that and just starts me off with a new instance of Jellyfin. I do appreciate your video though as it should work.
@@adamlewis3729 If you do this, then duplicate it, it should fix it.
You will first have to mount the config location in the old container:
1. Create a folder in the docker folder on your NAS named "jellyfin", then stop the container. Create a new volume pointed to that folder you just created and use the container path "/config". I left this part out in the tutorial because I stupidly assumed that people would only care about their media data.
2. Start the container, access the jellyfin folder on your NAS and confirm there is data inside of it. If there is, move on to step 3. If not, something isn't mapped properly.
@@WunderTechTutorials thank you so much! this is the missing step I needed!
unfortunately this method did not work to update my pi-hole docker container. the new version kept on crashing for whatever reason
Someone else had issues with the latest Pi-hole container. It sounds like it might be the container. Hoping that a new version is released soon.
I hate to be that guy but could you update this video to reflect the scenario of someone who has to mount the config location in the old container? Because I tried to follow the instructions you've written in the comments but for a noob like me it didn't work, I just ended up with a new setup every time. This was so confusing and frustrating I ended up removing everything and starting over, this time with a config location as you instructed in the comments. But this was anything but easy =/
Hey, this is still a valid way to do it, right?
Additional question: in the registry it says ":latest" (see @2:10) for both, the backup and the updated container.
When I download a new image and decide to turn the backup back on again because something didnt work with the new version of the image, will it use the old image from before? Im worried it will use the most recent image because of the ":latest" tag.
I want to update my 10 month old vaultwarden container and just want to make sure.
If you select "latest" for the new image your backup will use that too, right?
Therefore you'd always need to pick the specific version so that the image stays in docker, otherwise it'll just overwrite "latest" and you can't go back.
man wtf dude you fucked up my container. now when I try to go back to the older container it won't work. it keeps giving me a dead site with errors. when trying to open back the new container and trying to make a new short cut it keeps giving me a same log in site for the nas. now it won't work and im unable to use radarr now im fucked
The process outlined duplicates the container with the new version. As long as you didn't delete the old container (which you shouldn't have), just turn it on. If it's not working, it's for a different reason unrelated to this. The old container isn't touched if you followed this video as shown.