RAUDI VS watchtower

BTW if you have any tool in mind you can contribute, even just by suggesting the tool. If the Docker Image does not exist we will create and add it to RAUDI

I gave a second thought at your first question and we are adding the feature you asked. For the tagname the Docker Image will keep the same as the release version name of the tool. Here is the issue for this feature: Multi-dependency Docker Image

Hello, I am a Security Researcher working in an Italian startup that provides cybersecurity-related services. We use a lot of tools during our work we use Docker a lot. On the other hand, we hate to personally build Docker images for specific tools and keep them updated. So we created a tool called RAUDI (which stands for Regularly and Automatically Updated Docker Images) that automatically updates Docker Images every time there is an update using GitHub Actions. We started adding NetSec tools (since are the ones we use the most), but we plan to add every kind of tool that does not have an official Docker image on Docker Hub. Let me know if you like it or have any suggestions to make it better. Here is the link to the GitHub repo: - https://github.com/cybersecsi/RAUDI

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!