!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

403 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.122 Servers

Load older messages


SenderMessageTime
24 Mar 2026
@vcunat:matrix.orgVladimír Čunát
# Containers use systemd-nspawn, which requires pid 0 inside of the sandbox.
09:33:10
@vcunat:matrix.orgVladimír Čunát which adds uid-range into requiredSystemFeatures 09:33:34
@vcunat:matrix.orgVladimír ČunátPR https://github.com/NixOS/nixpkgs/pull/47810909:33:56
@jfly:matrix.orgJeremy Fleischman (jfly) @vcunat:matrix.org, how does https://github.com/NixOS/infra/pull/986 look? 11:05:36
@hexa:lossy.networkhexa
diff --git a/builders/common/nix.nix b/builders/common/nix.nix
index ce13643..79249e8 100644
--- a/builders/common/nix.nix
+++ b/builders/common/nix.nix
@@ -22,8 +22,11 @@
 
     settings = {
       accept-flake-config = false;
+      auto-allocate-uids = true;
       builders-use-substitutes = true;
       extra-experimental-features = [
+        "auto-allocate-uids"
+        "cgroups"
         "nix-command"
         "no-url-literals"
         "flakes"
@@ -32,6 +35,7 @@
         "kvm"
         "nixos-test"
         "benchmark" # we may restrict this in the central /etc/nix/machines anyway
+        "uid-range"
       ];
       trusted-users = [
         "build"
11:06:17
@hexa:lossy.networkhexasame changes that I did, but inline11:06:36
@hexa:lossy.networkhexastill, I'm wary of cgroups in cppnix11:06:47
@jfly:matrix.orgJeremy Fleischman (jfly) Or that :) 11:06:47
@hexa:lossy.networkhexaelated-minsky exposes uid-range feature now11:07:03
@jfly:matrix.orgJeremy Fleischman (jfly) I thought you said we used them, but I couldn't find evidence of that 11:07:26
@jfly:matrix.orgJeremy Fleischman (jfly) * 11:07:45
@jfly:matrix.orgJeremy Fleischman (jfly) It's an ungodly hour here. Feel free to merge, or close my PR. Good luck! 11:08:27
@hexa:lossy.networkhexawe reverted cgroups use because they broke builds11:10:02
@hexa:lossy.networkhexaover a year ago11:10:13
@hexa:lossy.networkhexaI know lix has them fixed11:10:26
@hexa:lossy.networkhexahttps://github.com/NixOS/nix/pull/1313511:11:07
@hexa:lossy.networkhexaoh and cgroups xp is likely not enough, right?11:12:18
@hexa:lossy.networkhexawe'd need use-cgroups, too11:12:23
@hexa:lossy.networkhexabut your example in the PR didn't either, so 🤷11:13:57
@jfly:matrix.orgJeremy Fleischman (jfly)Fun fact: the nspawn test container work uncovered a cgroups bug in lix (now fixed): https://git.lix.systems/lix-project/lix/issues/114311:15:28
@jfly:matrix.orgJeremy Fleischman (jfly)I don't think I have this enabled on my laptop where I have been running these tests11:15:57
@hexa:lossy.networkhexahttps://hydra.nixos.org/build/32472565111:16:08
@hexa:lossy.networkhexai think it requires /dev/net still11:16:40
@hexa:lossy.networkhexais that safe to leak into the sandbox though?11:16:50
@jfly:matrix.orgJeremy Fleischman (jfly) Hmm. This is failing to do networking between a nspawn container and a "classic" qemu vm. @kmein added that feature after I last worked on these. Lemme try locally 11:19:32
@hexa:lossy.networkhexa
 nix.settings.sandbox-paths = [ "/dev/net" ]; # to make nspawn↔qemu networking work
11:20:03
@hexa:lossy.networkhexathis is what the PR states11:20:09
@jfly:matrix.orgJeremy Fleischman (jfly)ooh ok11:20:38
@jfly:matrix.orgJeremy Fleischman (jfly)yeah, no idea if that's safe. perhaps it's a way to escape the sandbox11:21:16
@jfly:matrix.orgJeremy Fleischman (jfly)it looks like that didn't make it into the docs PR. i'll fix that right now11:22:29

Show newer messages


Back to Room ListRoom Version: 6