shepherd VS watchtower

Since watchtower doesn't support Docker Swarm I've come across shepherd but the author has stated that he wont be maintaining the project anymore which makes me reluctant to use it.

Shepherd for those of that run docker swarm.

Not at production (there are strict versioned images), but personally I use Shepherd in my distributed Docker Swarm (many hosts in different locations, even different architectures). I wonder why people say about some terrible issues. I must be very lucky: for over a year usage I've had only single one problem when service wasn't properly restarted (I remember it was Traefik). The only services excluded from auto-update are PostgreSQL and MongoDB (MariaDB works fine with auto updates).

Because all my Docker services are running in Docker Swarm I use similar project shepherd (available also at dockerhub). Not many features, but extremely easy to set up and it does its job (check, download and restart any service when new image is available, so I don't need to care about program updating at all).

I've used this for years

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!