• Nextcloud + OnlyOffice
  • *arr media management series (Lidarr, Sonarr, etc)
  • Gitea
  • Vaultwarden
  • PiHole
  • Jellyfin
  • Wiki-js
  • Lemmy
  • Prometheus/Grafana/Loki

Currently all containerised running on a debian VM on a Rockylinux Qemu/KVM hypervisor. Initially I was using rocky+podman but inevitably hit something I wanted to run that just straight up needed docker and was too much effort to try and get working. 🤷

Hardware is an circa 2012 gaming machine with a few ZFS raids for all of my Linux ISOs. It lives an extremely tortured existence and longs for the sweet release of death.

Toying with the idea of migrating it all to on-prem virtualised kubernetes cluster using helm charts to manage the stacks and using NFS mounts for persistent storage because I hate myself (and to upskill I guess)

What about you?

  • RatzOPEnglish
    2•1 year ago

    Basically I ran into issues with building images from newer and more complex compose files that podman-compose just couldn’t pull apart.

    Docker is still the go-to if you want shit to ‘just work’, it has an easier user experience, it’s what the vast majority of developers building containers are using. You can run rootless if you want without too much pain.

    It has come a long way but the probability that you’ll run into some random edge case or other issue with podman is higher, podman-compose has some thorns (high likelihood you’ll need to hack on compose files), if you want containers to start without your interaction you have to bake up systemd unit files for them, etc. I’ve not messed with podman-kube-play - wasn’t even aware of it, so can’t really comment as to how well that works.

    There’s nothing to lose by giving it a go except your sanity and time. 😁

    • @PriorProjectEnglish
      2•1 year ago

      Thanks for the insights. I’ll see how it goes.