-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Devbox cache restore fails on self-hosted runners #49
Comments
@LucilleH any thoughts on this? |
github-merge-queue bot
pushed a commit
that referenced
this issue
May 20, 2024
Addresses #49 The `runner` user on self hosted runners does not have access to `/usr/local/bin` path. This result in cache restore failures at `/usr/local/bin`. We can install devbox at user's home directory and make it accessible to subsequent actions.
@supershal Good call! Thank you for the suggestion and PR |
It seems that the line mentioned in the comment here wasn't fixed wit the PR.
|
@DjoleLepi you are right 😭 |
LucilleH
added a commit
that referenced
this issue
Jun 8, 2024
Update action.yml devbox CLI cache location. Addresses #49 Signed-off-by: Lucille Hua <lucille.hua@gmail.com>
github-merge-queue bot
pushed a commit
that referenced
this issue
Jun 12, 2024
Update action.yml devbox CLI cache location. Addresses #49 Signed-off-by: Lucille Hua <lucille.hua@gmail.com>
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
The devbox cache is restored to
/usr/local/bin/devbox
. https://github.com/jetify-com/devbox-install-action/blob/main/action.yml#L58This works well with github hosted runners. however self hosted runners runs as a
runner
user and they dont have permission to restore files outside home or workspace.As a result the cache restore fails.
Related issue filed at
actions/cache
: actions/cache#1127Various self hosted images are built from Dockerfiles at:
https://github.com/actions/actions-runner-controller/tree/master/runner
Should the devbox restored and installed at
~/.local/bin
directory and make it accessible by adding it to $PATH?The text was updated successfully, but these errors were encountered: