-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
github DynamicUser cannot access nix-daemon #473
Comments
That depends on the start order of the services. I think nix-daemon somehow only recognizes users that existed before it started. Generally I just remove all DynamicUsers that want to talk to the nix-daemon because of hard and seemingly time wasting bugs like this. |
@SuperSandro2000 I see, thank you. @zimbatm from looking at #50 it seems DynamicUser is being used for security reasons. The use case I'm trying to support is GitHub runners which can run (and cache locally in their nix store) eg Any suggestions what the best way forward would be? Once I better understand the correct approach I'm happy to file a PR. |
What supersandro suggested. Or add a dependency to the nix-daemon.service on this one to ensure the loading order. Most of our work is now going into https://github.com/nix-community/buildbot-nix, so this module will probably need to be removed at some point. |
Never mind, in the end I dropped srvos entirely and used nixpkgs github-runner directly. |
Running the following workflow file: https://github.com/siriobalmelli-foss/ci-test/blob/main/.github/workflows/aarch64-nix.yml
With the following role config:
Gives the following error:
I can work around this by adding:
I'm pretty sure the DynamicUser being created should be able to access
nix-daemon
, correct?I'm unsure however whether I would try to rework
srvos/nixos/modules/github-runners/default.nix
Line 58 in 1f867a5
nix.settings.allowed-users
or whether I should take another approach; any suggestions welcome.For context, this seems related to #50
The text was updated successfully, but these errors were encountered: