whats-up-docker VS watchtower

We use What's Up Docker [1] to monitor for new versions of docker containers that are created by others (eg. self hosted apps).

For containers we create ourselves, we automatically rebuild them each night which pulls the latest security updates.

[1] https://github.com/fmartinou/whats-up-docker

If your apps are container images, then there are tools like diun, watchtower and whatsupdocker, those can watch the image repository (like Docker Hub) and notify you if a new/updated image has been found. Some can even download and auto-update for you, but that comes at some risk of course.

I’m going to look into this soon since it seems a bit more accessible: https://github.com/fmartinou/whats-up-docker

A combination of https://github.com/fmartinou/whats-up-docker and docker compose

Might take a look at what's up docker https://github.com/fmartinou/whats-up-docker

I haven't tried it yet but this project aims to make updating docker containers a lot easier instead of just blindly trusting pull cronjobs or watchtower to work, apparently depending on the registry it can differentiate between minor/major updates and handle them differently: https://github.com/fmartinou/whats-up-docker

https://github.com/fmartinou/whats-up-docker Better than WatchTower IMO

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!