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

ci: fix toolchain #2061

Closed
wants to merge 6 commits into from
Closed

ci: fix toolchain #2061

wants to merge 6 commits into from

Conversation

rvolosatovs
Copy link
Member

Alternative soluton to #2060 , which should prevent such situations from occuring in the future by relying on all packages locked in a lock file and cached via nix.
That also means that we can manage our rust toolchain version and components in one standard location (rust-toolchain.toml)

haraldh and others added 2 commits July 15, 2022 10:24
```
Run actions-rs/toolchain@v1
/runner/_work/_temp/5a8c1328-61cf-4c6e-8a44-0a2477ad5648 --default-toolchain none -y
info: downloading installer
info: profile set to 'default'
info: default host triple is x86_64-unknown-linux-gnu
info: skipping toolchain installation
Rust is installed now. Great!
To get started you may need to restart your current shell.
This would reload your PATH environment variable to include
Cargo's bin directory ($HOME/.cargo/bin).
To configure your current shell, run:
source "$HOME/.cargo/env"
/root/.cargo/bin/rustup show
Default host: x86_64-unknown-linux-gnu
rustup home:  /root/.rustup
installed toolchains
--------------------
error: no default toolchain configured
Error: The process '/root/.cargo/bin/rustup' failed with exit code 1
```

Signed-off-by: Harald Hoyer <harald@profian.com>
Signed-off-by: Roman Volosatovs <roman@profian.com>
@github-actions github-actions bot added the infrastructure General issues around project infrastructure label Jul 15, 2022
@rvolosatovs rvolosatovs force-pushed the fix/toolchain branch 2 times, most recently from 34e0b2e to 5454c2f Compare July 15, 2022 09:42
Signed-off-by: Roman Volosatovs <roman@profian.com>
Signed-off-by: Roman Volosatovs <roman@profian.com>
Signed-off-by: Roman Volosatovs <roman@profian.com>
Signed-off-by: Roman Volosatovs <roman@profian.com>
@rvolosatovs
Copy link
Member Author

This would not work in existing self-hosted runners out-of-the-box. It would require one of the following changes:

  1. Getting docker (aliased to podman potentially) available on self-hosted runners
  2. Getting nix installed by default on self-hosted runners.
  3. Set up USER env variable on self-hosted runners, which may let us use the existing install-nix-action, refs Breaks on (at least some) self-hosted runners cachix/install-nix-action#98
  4. Don't know if podman is available already, but we could also run containers via podman directly Add option to run containers with podman instead of docker actions/runner#505

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

Successfully merging this pull request may close these issues.

None yet

2 participants