I like this although I would not have chosen Docker. Podman comes with no socket and rootless by default, it just seems more in line with this sort of architecture, not to mean Podman Quadlets and honestly, I would think it's better with git tracking but to each their own.
I probably wouldn't have chosen Debian. It'd probably be easier to use a RHEL spinoff like Alma or Rocky Linux.
Thanks for the feedback! I agree. I do have a comment on this, to explain my choice:
> Podman vs Docker
You may point to Podman here because Podman is natively rootless and doesn't require a daemon and additional workarounds to run rootless. I agree. However, Docker in rootless user nesting is also robust and possible, and I decided to stick to the docker-compose.yml because it is still the industry (and homelab) standard. This minimizes the time I need to translate examples or templates. Docker in rootless and Podman are mostly interchangeable at this level. Both run processes in isolated Linux namespaces on your host VM (not the Hypervisor!).
This is not 100% and may change anytime. I guess, for me, at this time, the difference between Docker in rootless and Podman is just too small, and the time needed to migrate all my docker-compose.yml's too much, to make the jump. Overall, it is not a critical decision for this architecture, more a choice.
Regarding Debian is similar, I just stick with what I am familiar with. Debian also never lost me.
I like this although I would not have chosen Docker. Podman comes with no socket and rootless by default, it just seems more in line with this sort of architecture, not to mean Podman Quadlets and honestly, I would think it's better with git tracking but to each their own.
I probably wouldn't have chosen Debian. It'd probably be easier to use a RHEL spinoff like Alma or Rocky Linux.
Overall, very nice!
Thanks for the feedback! I agree. I do have a comment on this, to explain my choice:
> Podman vs Docker You may point to Podman here because Podman is natively rootless and doesn't require a daemon and additional workarounds to run rootless. I agree. However, Docker in rootless user nesting is also robust and possible, and I decided to stick to the docker-compose.yml because it is still the industry (and homelab) standard. This minimizes the time I need to translate examples or templates. Docker in rootless and Podman are mostly interchangeable at this level. Both run processes in isolated Linux namespaces on your host VM (not the Hypervisor!).
This is not 100% and may change anytime. I guess, for me, at this time, the difference between Docker in rootless and Podman is just too small, and the time needed to migrate all my docker-compose.yml's too much, to make the jump. Overall, it is not a critical decision for this architecture, more a choice.
Regarding Debian is similar, I just stick with what I am familiar with. Debian also never lost me.
Proxmox is awesome