Open sellout opened 3 months ago
Did you find a way round this @sellout? Just got set up and having the same __noChoot issue even though sandbox is set in my flake.nix
@commandodev I don't think there is a way around it; garnix doesn't let you disable the sandbox (we are thinking of adding "actions" that take place entirely outside of a sandbox soon, but they won't be derivations).
@commandodev Yeah, what @jkarni said. For me the issue really was just the log content, and with the current garnix site, I use that directly way more than I look at GitHub logs.
My flakes have a ton of automation (thanks to Project Manager), so I generate a garnix.yaml that excludes derivations with __noChroot
.[^1] Which also means I don’t run into this particular message on GitHub any more, so I don’t even know if it’s still an issue.
[^1]: Correspondingly, my project configuration generates GitHub & Renovate configs that only allow auto-merging of PRs if the repo doesn’t have any __noChroot
derivations (i.e., where I can be sure that garnix is checking everything).
This GitHub job has very unhelpful logs:
but when I click through to the garnix build, it’s very clear what’s happening: