In this context, I think the prime advantage would be that instead of:
- Managing/setting Ubuntu/$distro for the host
- Installing Docker compose on host
- Writing a docker-compose.yaml file to declare your container architecture
- (potentially) Writing a systemd service to bring docker-compose up with the host boot
You just:
- Mange/setup nixos
- Add container architecture definition to nixos config
The containers, being systemd units, would have all the normal systemd log management like the rest of your system, instead of having to dig through docker-compose logs with a different mechanism than "normal" systemd service logs.
You'd also get all the normal benefits of a nixos system: the config file can be placed on a new system to completely reproduce the system state (modulo databases et all), rollbacks are trivial, etc.
You just: - Mange/setup nixos - Add container architecture definition to nixos config
The containers, being systemd units, would have all the normal systemd log management like the rest of your system, instead of having to dig through docker-compose logs with a different mechanism than "normal" systemd service logs.
You'd also get all the normal benefits of a nixos system: the config file can be placed on a new system to completely reproduce the system state (modulo databases et all), rollbacks are trivial, etc.