Bierochs (Page 246)

nginx-proxy-manager

Upgrade to Nginx Proxy Manager 2.9.22

No problems automatically updating the Docker image and run the container by Watchtower. Also executing recommanded backup of data. v2.9.22

pi-hole

Upgrade to Pi-hole 2023.03.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. 2023.03.0

rocket.chat

Upgrade to Rocket.Chat 6.0.1

No problems automatically updating the Docker image and run the container by Watchtower for Bierochs and Tanzcrew teams. 6.0.1

matomo

Upgrade to Matomo 4.14.1

No problems automatically updating the Docker image and run the container by Watchtower. Matomo 4.14.0 and 4.14.1

GitLab

Upgrade GitLab Runner to chart version 0.51.0 and app version 15.10.0

No problems deploying to K3s cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach. Helm Chart 0.51.0 v15.10.0 (2023-03-17)

git

Upgrade to GitLab 15.10.0

No problems automatically updating the monolithic Docker image and run the container by Watchtower. GitLab 15.10 Release

flux

Upgrade to Flux 0.41.2

Updated successfully via Homebrew and CLI bootstrapping Proxmox VE K3s Kubernetes cluster. v0.41.2

redis

Upgrade to Redis 7.0.10

Successfully upgraded the Docker container on the Database Host by means of Watchtower container and on the Mastodon instance manually with Docker compose. Redis 7.0 release notes

home-assistant

Upgrade Home Assistant to chart version 0.3.3 and app version 2023.3.5

No problems deploying two Home Assistant major versions to Proxmox VE K3s Kubernetes cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach. 2023.3.5 Helm Chart 0.3.3

ghost

Upgrade to Ghost 5.39.0

On both domains I upgraded Ghost successfully by means of Watchtower Docker container update. v5.39.0

mastodon

Upgrade to Mastodon v4.1.1

Minor update of container without any issue by means of Docker compose YAML infrastructure and automated Portainer GitOps workflow. v4.1.1 The database health check in the Docker compose file has to be updated to look like, which are indeed the default values: healthcheck: test: ['CMD', '