Proxmox

Ansible is one of my favorite things to use in my home lab for automating the tasks I dislike, and it's perfect for Proxmox updates with the community.proxmox.proxmox_pct_remote collection module installed. Once that's available, we can create a playbook that creates a dynamic inventory of your Proxmox LXCs and other containers, so that you can call them in other Ansible playbooks: Then we create a playbook like this, that will update Debian/Ubuntu LXCs. If you have other LXC bases, you can adjust accordingly for the package manager, and for the Proxmox tag group that you mihght have them sepa

The decision really comes down to two things: what hardware you already have running, and whether you want to run Pi-hole as a dedicated service or alongside other containers. Use the native install (Raspberry Pi, Ubuntu, or Proxmox LXC) if: You want a dedicated Pi-hole instance with minimal other services running on it You’re running Pi-hole on a Raspberry Pi or any Debian-based Linux distribution You’re running it in a Proxmox LXC and don’t need Docker on top You want the simplest, most-supported setup with the least amount of moving parts Use the Docker install if: You already use Docker

Instead of dynamically building VM images on every provision, I used existing Proxmox VM templates. My templates already had cloud-init enabled, SSH access configured, and base OS packages installed. This gave me: Faster VM provisioning — no image builds in the critical path Better control over OS hardening — managed outside the Kubernetes workflow Easier debugging — when something goes wrong, the VM layer is a known quantity