Skip to content
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

Do not attempt to install kvm on self-hosted runners #132

Open
dpc opened this issue Nov 20, 2024 · 0 comments
Open

Do not attempt to install kvm on self-hosted runners #132

dpc opened this issue Nov 20, 2024 · 0 comments

Comments

@dpc
Copy link

dpc commented Nov 20, 2024

I have a CI that have some things working on self-hosted runners, and some on normal Github runners.

Currently, after switching:

-      - uses: cachix/install-nix-action@v30
+      - uses: DeterminateSystems/nix-installer-action@v16

The CI fails on self-hosted runners, because it tries to install KVM, but there is no sudo.

It seems to me that if the Nix was already installed, the machine is probably a self-hosted one, and there's no point trying to install KVM.

I will probably end up disabling KVM, but ideally I would be happy to have it enabled on non-self-hosted machines.

Edit:

Seems like currently the existing Nix installation is not even correctly detected.

self-hosted runners just have nix in the PATH, and do not actually require installing anything. The action is still useful if it needs to run on a Github Actions standard runner in a VM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant