!BgJZHVOYkwVcEKLAyM:nixos.org

NixOS Deployments

1232 Members
NixOS Deployment tooling306 Servers

Load older messages


SenderMessageTime
30 Jun 2021
@zhaofeng:zhaofeng.liZhaofeng Li Church 23:11:35
@noah:matrix.chatsubo.cafeChurchYeah gonna try this from a nixos host, was originally trying this on a ubuntu laptop23:12:25
1 Jul 2021
@zhaofeng:zhaofeng.liZhaofeng Li
In reply to @noah:matrix.chatsubo.cafe
Yeah gonna try this from a nixos host, was originally trying this on a ubuntu laptop
Ah, that could be the reason. The qemu binaries are in different paths than in NixOS so they may not be available in the sandbox.
01:19:39
@noah:matrix.chatsubo.cafeChurchYeah wondering if I can pass args to nix build from colemna01:20:12
@noah:matrix.chatsubo.cafeChurchSince I can get a nix build going fine for cross compiling01:20:21
@zhaofeng:zhaofeng.liZhaofeng LiThere isn't one right now, but I can add one pretty easily. Let me see if there is a good name I can use for it01:23:02
@noah:matrix.chatsubo.cafeChurch

Might be helpful to pass in something like:

--option system aarch64-linux --extra-platforms aarch64-linux
01:28:18
@noah:matrix.chatsubo.cafeChurchIf I could tailor that per node it'd be even better01:28:36
@zhaofeng:zhaofeng.liZhaofeng LiActually for that you can add it to the nix config to the machine01:29:02
@noah:matrix.chatsubo.cafeChurchOh really, this I didn't know.01:29:13
@zhaofeng:zhaofeng.liZhaofeng Li An option for "passing arguments to build" is trickier than it seems, because the supported arguments are different between nix build (nix3-build), nix-build and nix-store. It's hard to provide an option to pass arguments and then change the build mechanism underneath 01:30:41
@noah:matrix.chatsubo.cafeChurchYah makes sense01:31:05
@noah:matrix.chatsubo.cafeChurchIf I can just declare this in the machines config however that's fine01:31:16
@noah:matrix.chatsubo.cafeChurch Zhaofeng Li: More follow up questions, is there a way to specify using a remote builder for a specific node? 23:44:55
@noah:matrix.chatsubo.cafeChurchHmm looks like it does...23:47:00
@noah:matrix.chatsubo.cafeChurchIs there an example of the structure of it? That doesn't seem to be specified anywhere I can see in the repo or the PR adding it.23:52:28
2 Jul 2021
@zhaofeng:zhaofeng.liZhaofeng LiThere's an option to specify the machine file, but not per-machine. It's passed as `--options builders ` to the Nix command01:08:29
@zhaofeng:zhaofeng.liZhaofeng Li* There's an option to specify the machine file, but it's not controllable per-machine. It's passed as `--options builders ` to the Nix command01:08:48
@zhaofeng:zhaofeng.liZhaofeng LiIn the current setup, multiple machines are built at once. You can control how many machines are in a batch, but there isn't an option to separate a single machine out at the moment01:09:55
@noah:matrix.chatsubo.cafeChurchHmm is there an example of the machine file?01:13:17
@noah:matrix.chatsubo.cafeChurchI just need to define at least two builders, my local, and a remote for arm6401:13:37
@zhaofeng:zhaofeng.liZhaofeng LiI think it's something like ``` ssh://hostname aarch64-linux ```01:17:42
@noah:matrix.chatsubo.cafeChurchAh got it. Do I need to include a line for my local builders?01:21:17
@noah:matrix.chatsubo.cafeChurchSeems not, cool. Guess I'll see how this works.01:24:55
@noah:matrix.chatsubo.cafeChurch

Zhaofeng Li: Okay are remote builders used for only part of the build or distributing the load of it?
Rather then running the whole build on it?

Seems to work if my machine has binfmt enabled so it can build for aarch64 as well.

But if I turn that off so I can hopefully do all building on the remote machine it fails out due to being unable to build on the local host.

01:40:01
@noah:matrix.chatsubo.cafeChurchNever mind, error on my part I think.01:43:52
@noah:matrix.chatsubo.cafeChurchOr not, yeah seems I can only distribute the load. Should see about a patch to allow for specifying all building be done on a remote builder for a specific node.01:46:00
@spudly:murf.orgspudly Are there known issues with Nixops compatibility in Nixos now because of Python 2 dependencies? All of a sudden I'm unable to reference the nixops package, nixos-rebuild switch or home-manager switch are dying with error: certifi-2021.05.30 not supported for interpreter python2.7 errors. 01:57:56
@linus.heckemann:matrix.mayflower.deLinux Hackerman
In reply to @noah:matrix.chatsubo.cafe
Or not, yeah seems I can only distribute the load. Should see about a patch to allow for specifying all building be done on a remote builder for a specific node.
You can pass --max-jobs 0 to prevent local builds. Not for a specific node, but it's probably already useful?
06:31:48
@linus.heckemann:matrix.mayflower.deLinux Hackerman
In reply to @noah:matrix.chatsubo.cafe
Or not, yeah seems I can only distribute the load. Should see about a patch to allow for specifying all building be done on a remote builder for a specific node.
I think passing --extra-platforms '' will also disable building for anything other than the local platform locally.
06:32:54

Show newer messages


Back to Room ListRoom Version: 6