-
Notifications
You must be signed in to change notification settings - Fork 443
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
Run ReadME.md example, Bug Get FileNotFoundError: [Errno 2] No such file or directory: '/var/run/secrets/kubernetes.io/serviceaccount/namespace' #2436
Comments
Thank you for creating this @Yumeka999!
/area sdk |
I run python script code in physical machine which install k8s ls -la /var/run/secrets/kubernetes.io/
and ls -la /var/run/secrets/kubernetes.io/serviceaccount
|
here is result |
Usually, this folder should indicate the namespace where you run your Pod's container: Do you know how did you create the |
The Dir Is the python script in Quickstart could be run in local machine? |
I guess that the root cause is katib/sdk/python/v1beta1/kubeflow/katib/utils/utils.py Lines 29 to 30 in 867c40a
Even though Katib SDK recognizes based on |
That's right, and you can execute the above code from local machine and from the pod.
|
if i delete the dir |
when i delete the dir "/var/run/secrets/kubernetes.io/" and run the python code again There is the new exception , it's
|
Now my env: Kubernetes version:
Katib controller version:
Katib Python SDK version:
Kubernetes Python SDK version:
|
@Yumeka999 Please use the |
It's error in kubeflow-katib==0.15.0, I find there not exists paramter |
@Yumeka999 Please can you try to use Katib 0.17 and try this example: https://www.kubeflow.org/docs/components/katib/getting-started/#getting-started-with-katib-python-sdk |
OK, Thank you |
What happened?
when i use this code to test katib (ReadME.md example)
What did you expect to happen?
python run_katib.py
I get this error:
Environment
Kubernetes version:
Katib controller version:
Katib Python SDK version:
Impacted by this bug?
Give it a 👍 We prioritize the issues with most 👍
The text was updated successfully, but these errors were encountered: