I experimented with several ways to run my services:

  1. “regular” systemd services (services.glance = { ... };)
  2. nix containers (containers.glance = { ... };)
  3. podman containers (virtualisation.oci-containers.containers.glance = { ... })

and I must say I’m starting to appreciate the last option (the least nixos-y) more and more.

Specifically, I appreciate that:

  • I just have to learn the app/container configuration, instead of also backwards-translating from their config into the various nixos options (of course the .yaml or whatever configuration files are still generated from my nixos config, I just do that in a derivation instead on relying on a module doing it for me)
  • Services are sometimes outdated in nixpks (even in unstable - and juggling packages between stable and unstable is yet another complication)
  • I feel like it’s more secure (very arguable and also of very little consequence since everything is on my homelab… it’s mainly for the warm fuzzies)

Do you guys use one of the options above? Something different?

  • @towerful@programming.devEnglish
    1•1 month ago

    I’ve used proxmox with VMs running Debian for Docker Compose stacks.
    Most “get started quickly” tutorials are docker based, and building into a compose stack with dependencies is easy enough.
    Then a VM per stack (depending on isolation, duplication/redundancy and all that).

    I’ve recently started playing with k8s, and Talos Linux is amazing.
    I went from no-idea to k8s-yaml-hell faster than I could imagine. No need to configure kubernetes.