Colmena | 323 Members | |
| A simple, stateless NixOS deployment tool - https://github.com/zhaofengli/colmena | 110 Servers |
| Sender | Message | Time |
|---|---|---|
| 1 Dec 2022 | ||
| I'm trying to switch to use
I've tried adding | 18:54:45 | |
In reply to @zhaofeng:zhaofeng.lihas the eval-node-limit heuristic improved? Without an explicit limit it at least used to completely blow my laptop up | 18:56:02 | |
In reply to @ask-yourself:matrix.orgThis is because nix tries to call git as part of the flake evaluation, and presumably it's not on PATH for root when using doas (maybe it is with sudo?) | 18:57:05 | |
does just colmena apply-local work now? | 18:57:42 | |
| Because running the evaluation as your user makes sense | 18:57:50 | |
In reply to @linus:schreibt.jetztas in, I think setting privilegeEscalationCommand should make it work | 18:58:16 | |
I never use colmena apply-local. I always need to do sudo colmena-apply local (I thought this was normal!). Yes, sudo colmena-apply local currently works, yes. | 18:59:52 | |
| Also this is current doas conf:
| 19:00:22 | |
| with privilegeEscalationCommand set, it should work without sudo or doas, and colmena should invoke whichever it is | 19:00:49 | |
| and not evaluate or build as root, which is good because that's not necessary | 19:01:01 | |
deployment.privilegeEscalationCommand = ["doas"]; is also set. | 19:01:03 | |
right, then try plain colmena apply-local | 19:01:17 | |
In reply to @linus:schreibt.jetztThere hasn't been any change to the heuristic which assumes a constant memory size for each node. We can probably make the number bigger if people keep running into things like this. It's bit difficult to estimate the memory usage to evaluate a "typical" condig | 19:01:31 | |
In reply to @ask-yourself:matrix.org colmena apply-local --sudo should work | 19:01:40 | |
| The output of
| 19:01:54 | |
| oops, never mind what I said then | 19:01:56 | |
In reply to @zhaofeng:zhaofeng.liThis should work even after I turn of sudo for this machine? | 19:02:29 | |
| (And yes it does work, thank you.) | 19:02:50 | |
| It uses the privilegeEscalationCommand configured in the config | 19:02:52 | |
| `apply-local` doesn't run the escalation command by default. It seems a bit rude to do so, given that sudo cache exists and Colmena may end up doing dangerous things without prompt. Better make it explicit I guess. | 19:03:36 | |
| gosh frick, I wanted to test if the problem still exists and yes it very much does lol | 19:04:00 | |
| * There hasn't been any change to the heuristic which assumes a constant memory size for each node. We can probably make the number bigger if people keep running into things like this. It's bit difficult to estimate the memory usage to evaluate a "typical" config | 19:05:19 | |
Zhaofeng Li: colmena apply-local --sudo doesn't work once sudo is turned off though, and I want to turn sudo off. | 19:05:42 | |
| Hm, would it be appropriate to set the OOM score adjustment for the nix-eval-jobs process to avoid this kind of thing? | 19:06:28 | |
| Hmm, it should be using the `deployment.privilegeEscalationCommand`. Let me check | 19:06:41 | |
| Wait. I had that commented out. | 19:06:59 | |
| Don't waste your time checking yet, probably my error. | 19:07:09 | |
| also, the heuristic results in 52 workers for me which... I think is deep into inappropriate territory for 32G of RAM :D | 19:09:04 | |
| Argh, I keep forgetting Element Android has Markdown turned off by default. Another thing to set for each new client | 19:09:10 | |
Ok yeah, colmena apply-locall --sudo does not work with sudo turned off, even with deployment.privilegeEscalationCommand = ["doas"];. | 19:10:44 | |