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?

  • malteneussEnglish
    1·
    5 hours ago

    This is an important question for selfhosting, which there’s too little guidance. It should be systemd services somehow, but i want to deploy NixOS (the underlying platform) separate from independent collections of services (one collection per app/project) without having to use another tool or concept like Docker or Kubernetes… Also i’m really looking forward to NixOS “Contracts” https://github.com/ibizaman/selfhostblocks