dockcheck VS watchtower

As someone who knows just enough about Docker to be able to scratch together a docker-compose.yml every now and again only to promptly forget all the commands I need to ever maintain them going forward, I'm eternally grateful that dockcheck.sh prompts me to do this as a final step whenever I run it.

I’m a simple man. I upgrade everything via dockcheck, verify that everything still works, and if not restore from backup!

And I've personally made a script to selectively auto-update containers, or just check status. With the option to filter or exclude specific containers. Find the project here: mag37/dockcheck

To "mass-check and mass-update" containers from the commandline, dockcheck is very light and useful. A simple dockcheck.sh -a -p for example would check all deployed containers for image updates and if there are any, pull them, then restart the container and at the end, cleanup unused images to free up diskspace. There is also a version with a web interface, DCW.

I haven’t gone the watchtower route, since I’d prefer to review changes myself (or let’s be honest - others’ reactions to the changes). Instead. I’ve been using a combo of diun and dockcheck (https://github.com/mag37/dockcheck ). Diun lets me know when containers have changed and dockcheck lets me cherry pick what I upgrade.

If you want to update images, try dockcheck or DCW.

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!