Running Plex in a Docker Container on Synology is Super Easy

Over the last couple of months I’ve been playing around with a bunch of self-hosted projects using Docker containers on my Synology NAS. In my most recent sponsored video for Plex, we take a look at spinning up a Plex server inside a container using Synology’s new Container Manager on DSM 7.2.

One might wonder, why use Docker when you can simply install Plex from the Synology package center? The answer lies in the flexibility and advantages Docker offers. Docker containers provide backup and migration opportunities that are more straightforward than other methods. They also offer a level of isolation, enhancing security. In the case of Synology specifically, the Docker versions tend to get updated more frequently, ensuring you always have the latest features.

Before diving in, ensure your Synology NAS is compatible with Docker. Synology’s website has a list of compatible devices that work with their Container Manager. If you are a Plex Pass holder and want to enable hardware transcoding you’ll also need to ensure your Synology NAS is running with an Intel processor that’s compatible with QuickSync video encoding. You can learn more about video transcoding in another video I made on that topic.

My video will take you step by step through the installation process by using a Docker Compose file to configure the container. If you’d like to see the one I’m using you can download it here.

Setting up Plex on Synology NAS using Docker was one of the more straightforward Docker projects I’ve undertaken. The process is efficient, and the benefits, especially in terms of backup and migration, make it worth considering for your next install.

New Synology How To: Using Docker Containers with the new Synology Container Manager

In my latest video we veer off into the nerdy weeds with a detailed step-by-step tutorial about how to spin up and manage complex Docker applications using the new Synology Container Manager that can be found in DSM 7.2.

As I mentioned in my previous video about my self hosted projects, there are hundreds of amazing open source applications out there that offer similar functionality to popular cloud apps. I received so many questions and comments from that video about how I get them running via Docker on a Synology NAS, so that’s where this video comes in.

Because the Docker containers run in an isolated environment, they’re a little more secure than just running applications on the NAS directly. They’re also very easy to back up and move to another server if needed. Just copy the folder over to the new machine, rebuild the containers with a mouse click, and migration is done!

In the video I demonstrate installing Wallabag, an open source “read later” application similar to Pocket and Instapaper. The way it works is that Wallabag will download an archive of a provided URL, transform the web page into a readable format with just the content, and make it available for offline reading via a web browser. The Wallabag app for Android and iOS can sync the Wallabag container’s data with a phone or tablet.

Wallabag runs on the NAS in a container and its data is stored locally there as well. Using Tailscale I’m able to connect back to the application from anywhere in the world securely without having to open up any ports on my router.

I chose wallabag for this demonstration because it’s an example of a project that consists of multiple Docker containers working in concert with each other. In this case there’s the main Wallabag application in one container, a mysql database server in another and a third container runs a redis caching server.

In the past it was possible to get a project like this working but it had to be done outside Synology’s Docker app using the command line or another tool. Container Manager now makes it possible to build and run applications like this without having to use anything else.

In the tutorial I detail the steps of finding and editing Wallabag’s Docker Compose file and building the application as a “project” inside of Container Manager. One of the important things in this process is pointing the containers to a directory on the NAS for storing data. Containers are considered expendable with each update or build, so user data has to be mapped to a persistent storage location on the NAS. After trouble shooting a few minor error codes I was able to get Wallabag project built and operating relatively quickly and reliably on the NAS.

While all of this might seem a bit daunting vs. finding an app and hitting the install button, containerized applications are in many ways the new standard for running open source applications like this. While there is some up-front complexity, the advantages of having what is essentially portable versions of very robust server applications save far more time in the future. Should something ever happen to my NAS I just need to restore the backup files to a new location, click the build button, and I’m back exactly where I left off.

Let me know what you think in the video’s comments! Also be sure to share some of the containers you’ve found to be most useful.

Disclosure: Synology is an occaisional sponsor here on the channel and they provided me with the NAS hardware used in the review free of charge. However they did not sponsor this video nor did they provide any input or approval prior to publishing.

Using Docker to Add RTSP Functionality to WYZE Cameras via a Synology NAS

Yes this headline is a mouthful! But I stumbled across a great solution for Wyze camera users who want to keep their cameras up to date yet still use them via RTSP to their own security NVRs. Setting this process up is the subject of my latest “how to” video.

With Wyze pulling their official RTSP firmware some super smart community members figured out a way to build a “bridge” that takes video out of the Wyze cameras and makes that video available as an RTSP, RTMP or HLS stream that can be used by any compatible security DVR/NVR. It does this through the use of a Docker container that can run on just about any compatible Linux based device.

Once installed and logged into your Wyze account, any compatible camera on the same network as the computer hosting the container will be available. Your security NVR will connect to the stream on the container which will in turn bridge the video from the camera. Since this process mostly passes a relatively low bandwidth video stream it’s not very resource intensive and even a Raspberry Pi can get the job done.

As of the time of this writing it’s compatible with most Wyze cameras with the exception of their new “OG” cameras and their Video Doorbell Pro. It’s likely Wyze is disabling whatever loophole existed in their older hardware to prevent this circumvention around their subscription services on newer devices. You can learn more about their push to subscriptions in my recent video on the topic.

In my Docker how to video we connected my cameras to Synology’s Surveillance Station – a pretty robust NVR that’s included with most Synology NAS devices. I did a tutorial series a few years ago on it. But this should work with just about anything including some of the popular open source projects.

Docker is something I’ve been learning about over the last year or two and this is a great first project to play with if you’re interested in dipping your toes into containerizing applications. Synology has a great graphical Docker interface that helped me wrap my head around how it all works.

If you’d like to learn more about Docker I found this video from Networkchuck to be a great summation of its power and potential.