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

nix profile install fails on ubuntu-24.04-arm runner #222

Closed
msgilligan opened this issue Jan 16, 2025 · 2 comments
Closed

nix profile install fails on ubuntu-24.04-arm runner #222

msgilligan opened this issue Jan 16, 2025 · 2 comments

Comments

@msgilligan
Copy link
Contributor

msgilligan commented Jan 16, 2025

I am using install-nix-action to build secp256k1-jdk and it works perfectly for ubuntu-24.04 and macOS-14. I opened a PR to add ubuntu-24.04-arm and I get the following failure during nix profile install:

nix profile install nixpkgs#secp256k1
  shell: /usr/bin/bash -e {0}
  env:
    JAVA_HOME: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/23.0.1-11/arm64
    JAVA_HOME_23_ARM64: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/23.0.1-11/arm64
    TMPDIR: /home/runner/work/_temp
error: getting status of '/home/runneradmin/.config/nix/registry.json': Permission denied
Error: Process completed with exit code 1.

I'm not sure what difference in the -arm runner is causing this, but hopefully there is a way to resolve this.

@msgilligan
Copy link
Contributor Author

msgilligan commented Jan 16, 2025

I created PR #221 to run the tests for install-nix-action on the GitHub ARM runner and this failure looks related:

https://github.com/cachix/install-nix-action/actions/runs/12817083173/job/35739671809?pr=221

Run cachix use cachix
  cachix use cachix
  shell: /usr/bin/bash -e {0}
  env:
    nixpkgs_channel: nixpkgs=channel:nixos-24.11
    oldest_supported_installer: nix-2.8.0
    NIX_PATH: nixpkgs=channel:nixos-24.11
    TMPDIR: /home/runner/work/_temp
cachix: /home/runneradmin/.config/nix: createDirectory: permission denied (Permission denied)
Error: Process completed with exit code 1.

@msgilligan
Copy link
Contributor Author

It looks like the issue I am seeing was caused by this upstream issue: actions/partner-runner-images#27

The workaround in that issue solved my problem.

I'm going to close this since we have PR #221 to track the upstream issue.

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