Updating Docker Containers in a Synology NAS [Video Request]
HTML-код
- Опубликовано: 6 июл 2024
- In this video we cover how update Docker containers in a Synology NAS.
Donate here:
www.paypal.com/cgi-bin/webscr...
Bitcoin here: 19JXFGfRUV4NedS5tBGfJhkfRrN2EQtxVo
Timecodes
0:00 - Start
0:05 - Intro
1:26 - Updating using the Latest tag
8:28 - Updating using Versioned tags
9:46 - Outro Наука
Ha. Had two questions after setting my NAS up following your instructions a month ago. Came back to your channel and I see you have both questions answered! This one, plus the one about the torrents never being removed. Well done!
Hope your channel takes off! Saludos Jorge!
Hola! El nombre me suena pero no estoy seguro de donde.
Thanks for posting this! It is very helpful.
Great info; Thank you
Hi! Would it be a good idea to automate this using 'Watchtower'? Perhaps it could be a topic for a video?
I would say that it makes sense if you are running Docker on a system that you fully control. In a Synology NAS, I would probably stay away from trying something like that as they build a lot of customization into how Docker works.
Additionally, this series was about helping people who are beginners at using containers in a GUI based system.
Maybe I can explore doing a video like that in the future for another type of setup. Thanks for the suggestion.
Thanks for the video! I did have a question though.. I have the same setup for qbitt but cannot figure out how to update it as the container has the vpn in the container with it. Any advice on how to update it?
Thanks!
I do the same thing that I describe here with QBitTorrent-VPN image. So, it should work.
I noticed in your video that you've stopped several containers, such as "prowlarr," and only a few are "running." Could you please explain the rationale behind starting and stopping containers? When do you enable or disable them?
Hi! The NAS that you are seeing in my videos is not my main NAS. It is a virtual NAS that I set up just for the RUclips series. I don't need these applications running all the time in it and that's why I turn them off. In a real use scenario, you want your applications to be up all the time.
In my personal NAS, I strive to keep the apps running non-stop.
Hi, thanks for the work. I mapped my containers correctly and everything has been working fine. However, when I updated the containers all my data was lost.When I went to the config folders they are all empty Now I have to reconfigure everything. Any ideas why/how, also how to ensure it doesn't happen again.
Weird. Did you use the Linuxserver images?
Other images don't put the config files in the /config folder that I map to the container.
Yes, I have no idea why. I think I may have upgraded images incorrectly. That is the only this I can think of.
It's kinda hard to follow what you are doing, I don't know if we are using different DSM version? I tried doing the reset but still see old version of Sonarr.
1. Stop the running container
2. Download the latest image again
3. Reset the container
4. Restart the container, this time, it will start from the fresh version of the image that you downloaded.
Simple actually.
@@techbytetips I don't get the option to restart the container after I have done the reset, it just stays grayed out. So when I click start it just keeps loading the old image. Don't know why this is happening or what I am doing wrong
@@showdown2006 Not sure what could be causing that. I haven't used DSM 7.2 which changed Docker to Container Manager. But it should behave the same. Try restarting the NAS and seeing if that solves the issue.
@@techbytetips I completely started over and installed latest image. Seems to be fine now.