containarr VS watchtower

not with containarr

Hijacking: I have an example of a good practice here. Feel free to look through the repository's structure, and the configurations in use for inspiration.

quick update: Making alternate configs is a bit more involved than I thought because I hadn't thought about it much. This is being addressed in milestone v0.3.0

"Hi, this is ray the developer of containarr. /u/bigbeansinyachin is an alt account that I made before this one because, well, I hadn't really intended to make a permanent reddit account again before now. But, in the interest of accepting reddit's value in spuring discussion I've decided to change my stance. You can check further development by following at https://github.com/ray-rock/containarr or by going to my account and following up there. I will be back when its time to drop the newest release. In the meantime, I'd like to thank everyone who has participated in this discussion, and those who have followed up on github. Your feedback helps drive this project and introduces me to new concepts, tools, and approaches I might not have otherwise considered. I'll check back periodically to gather/reply to any new feedback before the next release."

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!