git
Upgrade to GitLab 17.1.1
No problems automatically updating the major version monolithic Docker image and run the container by Watchtower. GitLab 17.1 Release GitLab Critical Patch Release: 17.1.1, 17.0.3, 16.11.5
docker
GitLab
Upgrade GitLab Runner to chart version 0.66.0 and app version 17.1.0
No problems deploying GitLab Runner to K3s cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach. And also by means of Watchtower infrastructure to Docker host for Image Lifecycle Management. Helm Chart 0.66.0 v17.1.0 (2024-06-20)
🌙🐄 Moone Update 2024 | Revision A
So very easy manual upgrade, done within no time and no problems whatsoever with this dockerized mailcow instance. 🌙🐄 Moone Update 2024 | Flatcurve Update Phase I 🌙🐄 Moone Update 2024 | Revision A
vault
Upgrade to Vault 1.17.1
No problems upgrading the Hashicorp Vault Docker container with a Docker compose yaml file within Portainer and by means of Portainer DevOps resp. GitOps. v1.17.1
metabase
Upgrade of Metabase v0.50.8
No problems upgrading the Docker container with a Docker compose yaml file and by means of Watchtower infrastructure. Metabase v0.50.8
ghost
Upgrade to Ghost 5.87.0
On both domains I upgraded Ghost successfully by means of Watchtower Docker container update. v5.87.0
rocket.chat
Upgrade to Rocket.Chat 6.9.3
No problems automatically updating the Docker image and run the container by Watchtower for Bierochs and Tanzcrew teams. 6.9.3
elastic
Upgrade to Elasticsearch 7.17.22
Successfully upgraded the Docker container on the Mastodon instance manually with Docker compose and fully automated on k3s Kubernetes cluster by gitops. Elasticsearch version 7.17.22
pi-hole
Upgrade to Pi-hole 2024.06.0
On all three nodes I upgraded Pi-hole successfully by means of fully automated Watchtower Docker container update. On the CentOS 7 VM i had to recreate a sym-link to /etc/lighttpd/conf-enabled/99-unconfigured.conf within the container. ln -s /etc/lighttpd/conf-available/99-unconfigured.conf /etc/lighttpd/conf-enabled/99-unconfigured.conf 2024.
dependency-track
Upgrade to Dependency-Track 4.11.4
No problems upgrading the Docker container with a Docker compose yaml file within Portainer and by means of Portainer DevOps resp. GitOps. frontend 4.11.4 apiserver 4.11.4 Dependency-Track Change Log
ghost
Upgrade to Ghost 5.86.2
On both domains I upgraded Ghost successfully by means of Watchtower Docker container update. v5.85.1 v5.85.2 v5.86.0 v5.86.1 v5.86.2
lam
Upgrade to LDAP Account Manager 8.8
Automated minor container update without any issue by Watchtower. LAM 8.8 with enhanced request access module