Automatically updating podman containers

URL: Documentation on docs.podman.io Podman has a service, that can be enabled on a per user basis, that allows podman to automatically update a container, when it detects a new version of the container image. This service is called podman-auto-update and is installed with podman, along side a .timer file aswell. The service: $ systemctl --user status podman-auto-update.service ○ podman-auto-update.service - Podman auto-update service Loaded: loaded (/usr/lib/systemd/user/podman-auto-update.service; disabled; preset: disabled) Active: inactive (dead) Docs: man:podman-auto-update(1) The timer:

K3S-HA-Cluster, running on raspberry Pis, controlled from a container

This project saw the light of day, after testing Techno Tims excellent K3S with etcd setup, using ansible. I highly recommend you check it out here: Fully Automated K3S etcd High Availability Install on technotim.live . I am trying to learn how to use kubernetes, and after trying and failing to set up a full K8S cluster on my 3 Raspberry Pi 4 2GB’s, i found Techno Tims fantastic video on setting up a K3S cluster with ansible (find it here: Techno Tims video on Youtube ), I decided to give it a go.

Gitea Actions

Documentation at Gitea: https://docs.gitea.com/usage/actions/overview Gitea Actions is a CI/CD Automation tool, like (and compatible with) Github Actions. Gitea Actions uses Act Runner as its medium of running the desired workflows. It does this, by creating one or more containers that the jobs run inside of. When a job is done, the container is deleted again, and the runner is now ready for the next job. How to run it? Gitea Actions Act runner, can either be installed directly on a host computer (this can be the same hosts that Gitea is installed on, or a different one), or run in docker containers.