dockcheck-web VS watchtower

DockCheck Web

So now I use Dockcheck Web nice and simple web page, notifications via Telegram and others. - it's based off of a bash script

I use Dock Check web to get a web page of containers that can be updated. It has notifications via telegram, email etc... Then use portainer to update the ones I want.

Hi, I am the creator of dockcheck-web

I also added support for arm64 My future plan is to make a slim version of dockcheck-web without the webgui. "Dockcheck-slim" with notifications. I have changed the layout for the compose file a littlebit, so make sure to checkout the readme on github.

Also make sure to check out this spin-off webgui/notification project: Palleri/dockcheck-web

Documentation

If there is away to escape this container with apparmor or SELinux enable please let me now on my github [Palleri](https://github.com/Palleri/dockcheck-web)

dockcheck-Web is a spinoff project by u/Palleri and is a great and simple way to just add a monitoring frontend to this script. Currently I don't think there's a way to update from the web, as I think that'd require you to mount your whole docker-root directory for paths.

If you're interested - my mate also made a webgui front for this project, for monitoring: Palleri/dockcheck-web

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!