!VhzbGHamdfMiGxpXyg:robins.wtf

NixOS LXC

37 Members
lxc, lxd, incus discussions related to NixOS15 Servers

Load older messages


SenderMessageTime
6 May 2025
@hexa:lossy.networkhexaright17:19:49
@hexa:lossy.networkhexabut it exists and it pays the bills17:19:54
@adam:robins.wtfadamcstephensi use cloud-init for non-nixos, on the rare occasion i spin one up, but i'm also only interested in bootstrapping my user environment17:22:14
@hexa:lossy.networkhexaI don't get the appeal of full os containers tbh17:22:32
@hexa:lossy.networkhexafeels like a nieche17:22:50
@hexa:lossy.networkhexa* feels like a niche17:23:16
@adam:robins.wtfadamcstephensi use them so that there's not the VM overhead, but allows me to keep services off the host.17:23:22
@adam:robins.wtfadamcstephensthere is less isolation though, so it's a trade off17:23:45
@hexa:lossy.networkhexayeah, for services that I care about there is systemd hardening17:24:00
@hexa:lossy.networkhexaso I do run them on the host, privately of course17:24:10
@adam:robins.wtfadamcstephensyeah, that should be sufficient if the service is hardened17:28:47
@c0ba1t:matrix.orgCobalt
In reply to @hexa:lossy.network
I don't get the appeal of full os containers tbh
ProxMox (as much of a niche as it is) uses them quite well. They feel mostly like VMs, eliding some isolation, but the ease of admin (resizing storage, memory/CPU changes on the fly) is nice. Proxmox + LXC also integrates quite well
18:48:32
@c0ba1t:matrix.orgCobalt* ProxMox (as much of a niche as it is) uses them quite well. They feel mostly like VMs, eliding some isolation, but the ease of admin (resizing storage, memory/CPU changes on the fly) is nice. Proxmox + LXC also integrates quite well with NixOS 18:49:59
@adam:robins.wtfadamcstephens That's consistent with how you work with them in incus. They're just a separate instance type  19:09:23
@hexa:lossy.networkhexaThanks, but I'm staying far away from Proxmox.19:09:40
@hexa:lossy.networkhexaIt is a shitty webfocused stack written in Perl and some Rust these days19:09:56
@hexa:lossy.networkhexaBut they still can't do automatic placement19:10:08
@hexa:lossy.networkhexaand they don't support in place upgrades19:10:16
@adam:robins.wtfadamcstephens What? How do you upgrade it then? 19:16:30
@hexa:lossy.networkhexareboot19:34:42
@c0ba1t:matrix.orgCobalt
In reply to @hexa:lossy.network
and they don't support in place upgrades
Are you sure about that? I can just apt dist-upgrade which should get everything except the kernel.
20:06:22
@c0ba1t:matrix.orgCobaltOr am I misunderstanding how they do updates there? 20:06:40
@hexa:lossy.networkhexainstall needrestart and find out20:08:13
@hexa:lossy.networkhexaif you restart its services it will fence the host in a cluster20:08:26
@hexa:lossy.networkhexa* if you restart its services it will fence the host in a cluster setup20:08:28
@hexa:lossy.networkhexayou absolutely cannot restart some of its services20:08:38
@hexa:lossy.networkhexawhich is absolutely possible with incus (and ganeti, which Ive used for years befoer)20:08:53
@hexa:lossy.networkhexaproxmox is the badly designed outlier here20:09:02
@hexa:lossy.networkhexathey also don't control the basis for the cluster protocol, which is based on corosync20:09:37
@c0ba1t:matrix.orgCobalt
In reply to @hexa:lossy.network
install needrestart and find out
Thanks for that hint, I should likely restart my hosts more often then.
20:10:10

Show newer messages


Back to Room ListRoom Version: 10