-
Notifications
You must be signed in to change notification settings - Fork 51
"Permission denied" error when not using the default namespace in hf_interactive notebook #129
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
"Permission denied" error when not using the default namespace in hf_interactive notebook #129
Comments
Is this connected to #125 ? |
My current thought is that this is an issue with the upstream image not being built to be compatible with running as an arbitrary user on OpenShift. I'm planning on rebuilding and pushing the image after adding something like:
as seen here If this works we can rebuild the images ourselves and push them to our quay org. Then we can see if Ray is open to adding this to their builds |
I was able to get the
which is available at quay.io/kpostlet/ray:2.1.0 if anyone else wants to use this for testing you can pass it to your cluster = Cluster(ClusterConfiguration(
...,
image='quay.io/kpostlet/ray:2.1.0'
)) |
This was added but reverted in the ray project. See ray-project/ray#32025 for discussion |
My current ideas are that we can either:
|
I've noticed the below permissions error while running the
hf_interactive.ipynb
notebook demo.This error occurs when I deploy my RayCluster in any namespace besides the default namespace. Simply using default overcomes the permissions issue. However, this is not behavior we want to support. We need to ensure that the actions of the codeflare-sdk have the required permissions in the correct namespaces.
This issue can be partially circumvented by adding
runtime_env = "env_vars": {"HF_HOME":"huggingface"}
to yourray.init()
command, however, it will just lead to a similar permission issue later on in training.How can we ensure that the users have the correct permissions in their namespaces?
The text was updated successfully, but these errors were encountered: