This repo contains some examples of how someone can use bootable containers to deploy a wide variety of applications.
The base images in this repo are based off the Fedora bootc image.
All images come with distrobox, cloud-init, and cockpit.
These images assume you are using cloud-init, kickstart, or similar tool to provision your hosts with things like desired hostnames, IP addresses, etc during initial boot.
The Containerfile contains multiple stages that can be used to get exactly the software you need. See Multi-stage Builds documentation for more information on how this works. For this repo, the image tag is the same as the build target name.
The GitHub Actions and Containerfile has support for private registry/repository if you uncomment the applicable lines.
The GitHub Actions also will create a SBOM of your image using Syft, run a vulnerbility scan using Grype, and upload the report to your Code Scanning page in the Security center of your repository. This will only work if your repo has Code Scanning enabled for your repository. See the GitHub docs for which repos can enable this.
This image simply installs k3s on our base image. Meant to be used as either server or agent.
WIP!
This runs as a quadlet and is configured by the nginx.conf which is placed in the /etc/nginx folder.
This quadlet will work out of the box but because there's no way to include secrets as part of the quadlet definition you will have to podman exec into the pod and change the password manually by running pihole -a -p to set a password. This is a one time operation.
This image installs Promethus on the host itself instead of using a container. Useful as a base image so observability comes baked into all your systems!