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
I0115 12:39:37.668298 26 cache.go:116] Connecting to cache endpoint 172.21.46.255:8887
WARNING: The directory '/home/test_user/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
ERROR: Could not install packages due to an OSError: [Errno 13] Permission denied: '/home/test_user/.local'
Check the permissions.
I0115 12:39:41.632095 26 launcher_v2.go:150] publish success.
F0115 12:39:41.632148 26 main.go:49] failed to execute component: exit status 1
time="2025-01-15T12:39:41.639Z" level=info msg="sub-process exited" argo=true error="<nil>"
Error: exit status 1
P.S. OpenShift executes the Pod as a random user. We use a workaround by setting group="root" to all files in the home repository, and setting permission 775.
RUN chown -R test_user:root /home/test_user && chmod -R 775 /home/test_user
Is there a better solution?
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered:
Environment
KFP standalone deployment according to https://www.kubeflow.org/docs/components/pipelines/operator-guides/installation/ on an OpenShift cluster v4.16.x
Steps to reproduce
Create a Docker image according to the following Dockerfile
Deploy it into some public repository, I deployed it as
quay.io/dataprep1/data-prep-kit/kfp-test:0.0.1
Create a very simple KFP pipeline:
Compile and deploy the pipeline.
Create a Run.
The KFP Pod fails with the following logs:
P.S. OpenShift executes the Pod as a random user. We use a workaround by setting group="root" to all files in the home repository, and setting permission 775.
Is there a better solution?
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered: