You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rig defaults to create a user package library (faq 1).
This can be unfortunate on linux, because when GHA runs a workflow inside a the container, it mounts $HOME to the host machine, so packages that were pre-installed by rig under ~/R in the container image are actually not available.
Perhaps it should only use a user package library if user != "root" ?
The text was updated successfully, but these errors were encountered:
Maybe we can change the default, actually. We could omit the user library by default if the (original) user is root. We need to be careful, because people do
sudo rig add ...
in which case we need to look up the original user. But I guess we are already doing that, to create the user library at the right place.
I decided not to change this now, since you could solve your original problem, and changing the installation location now could break people's workflows.
Please reopen or open a new issue if you have problems with this. Thanks!
rig defaults to create a user package library (faq 1).
This can be unfortunate on linux, because when GHA runs a workflow inside a the container, it mounts $HOME to the host machine, so packages that were pre-installed by rig under
~/R
in the container image are actually not available.Perhaps it should only use a user package library if user != "root" ?
The text was updated successfully, but these errors were encountered: