PMS_Updater VS watchtower

There is this script that updates you to the latest version and creates a backup you can run the script manually or automatically every week, works great.

You either wait for iXsystems to update the package they provide (and you can use the built-in updating feature). Or you go manually into the Jail and upgrade the packages there. You probably gonna need this shell script in your jail to fetch updates and update them.

The packaged python host is funky on a recent build. You can either follow the instructions here or download the file manually and provide that to the script

[Optional] Install a new copy of Plex in either a new jail or via plugin (not sure how you have it at the moment but the plugin tends to be quite out of date, although you can use PMSupdater.sh to keep it up to date. To update you then go into jails/command line and run "./PMSupdater.sh" which is super easy - but the "live" version and the plugin will be slightly off (who cares!) https://github.com/mstinaff/PMS_Updater Move the metadata from the old install to the new install (but if it works, why are you bothering reinstalling plex?)

libpython2.7.so is obviously a python dependency Check this to do the work around until you can update python.

1) Get 9020 and 300 (as DAS). Run everything in 9020 using Plex and MineOS plugin to run your Plex and Minecraft servers. You can use PMS_updater ( https://github.com/mstinaff/PMS_Updater ) to easily update Plex. Just need to install perl15. Forget the HP box.

Related: https://github.com/containrrr/watchtower

> if you're using the docker image, upgrades are a breeze. Just bump the tag on the image, redeploy, and you're done.

Or you could just run Watchtower beside it and it will automatically update your docker containers. https://github.com/containrrr/watchtower If you are OK with automated updates.

So i primarily use containers on my local machine walled off from the internet, so it's not a big concern for me. Watchtower [1] is popular among home server users too which automatically updates containers to the latest image.

For production uses I think companies generally build their own containers. They would have a common base linux container and build the other containers based off that with a typical CI/CD pipeline. So if glibc is patched, it's probably patched in the base container and the others are then rebuilt. You don't have to patch each container individually, just the base. Production also minimizes the scope of containers with nothing installed except what's necessary so they have few dependencies.

[1] https://github.com/containrrr/watchtower

You can use Watchtower (https://containrrr.dev/watchtower/) that solves problem of manual pulling on VPS.

I checked https://containrrr.dev/watchtower/ and Arguments, but I don't understand where to attach that using portainer.

Again, there are options to automate some of the burden here by using tools such as Watchtower.

Have you ever deployed a Docker app on a server, but everytime you push a new version of your image to a Docker registry you need to manually restart your app? If you want to automate this restarting, this blog post is for you! I am now going to show you how you can do this with literally 1 simple command using Watchtower!