docker-gen VS watchtower

Yeah, I usually do if I pass URLs to container. But again, the nginx config is completely auto-generated by docker-gen. Not sure why they don't use the container name, maybe duplicate container names? (if that's possible)

I've not got around to it, but I've always fancied creating a nice landing page that automatically updates as services come up/down, using the system jwilder created to make nginx-proxy, docker-gen. Could be a fun little project, anyway!

https://github.com/nginx-proxy/acme-companion https://github.com/nginx-proxy/docker-gen https://github.com/projectdiscovery/dnsx https://github.com/projectdiscovery/httpx https://github.com/projectdiscovery/mapcidr https://github.com/debauchee/barrier https://github.com/stedolan/jq https://github.com/ddosify/ddosify https://github.com/kubernetes-sigs/kind https://github.com/mailcow/mailcow-dockerized https://github.com/motiv-labs/janus

Then to make deployment super easy we're using nginx-proxy which uses docker-gen (and the acme-companion for automatic SSL cert generation) to automatically re-configure an nginx reverse proxy to point to your containers.

I've now got a setup using docker where the reverse proxy configuration is within the container's configuration (using nginx-proxy, which uses docker-gen). That way I just set the host, path, etc. in my container config, deploy, and the nginx servers are re-configured accordingly. No need to worry about ports and IPs then either.

I use an automated nginx reverse proxy. What this does is setup an nginx reverse proxy which uses docker-gen (follow the advice of setting it up separately). docker-gen listens for docker events such as a container being run, inspects that container for the details it needs (port, host, etc.) then configures the nginx accordingly.

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!