kbld VS watchtower

Pipe your manifest through https://github.com/vmware-tanzu/carvel-kbld before deploying. It will resolve the image tags to digests.

you can also use a tool such as kbld which is capable of taking yaml that has a floating tag or specifier, building your image, pushing it to a registry, and then emitting the same yaml but with the floating tag locked down into a SHA.

We use https://github.com/vmware-tanzu/carvel-kbld do workaround this issue. You can just pass your deployment.yaml to kbld and it will rewrite all image tags to their corresponding resolved digests. You can than pipe the result to kubectl apply or your deployment tool of choice (we use Kapp from the same developers as kbld).

From purely a container standpoint, for my home Kubernetes cluster, I use ArgoCD for deployment and wrote a little plugin to pipe the final manifests (generated through helm, kustomize, static files, whatever) through kbld. kbld replaces the image tag with the digest sha, which means ArgoCD sees it as a change to the manifest, and with auto-sync turned on deploys the latest image automatically. I've had my Argo applications configured this way for over a year with basically no issues.

kbld - Build or reference container images in Kubernetes configuration in an immutable way

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!