-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[JupyterLab] KubeFlow 1.8.0 - error when cloning repository #7413
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
/kind bug
What steps did you take and what happened:
![image](https://private-user-images.githubusercontent.com/86011874/283350605-20a6fe8f-db2e-41d4-8c33-eece020bab5c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIxMjIyNjksIm5iZiI6MTcyMjEyMTk2OSwicGF0aCI6Ii84NjAxMTg3NC8yODMzNTA2MDUtMjBhNmZlOGYtZGIyZS00MWQ0LThjMzMtZWVjZTAyMGJhYjVjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI3VDIzMTI0OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNiZmQ1MjkyYTY3YzY3MzJhNDc4ZGRlYTU3MzJlZTg4ZGIxOWUxMTM3ZmRiZDJjYTkyMzZhMjdlMDNmNzgzNDQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.VdNnrKLu63oyFZ6F-v1ZLvkzDhQKKcAz3MjXpi0OLGQ)
Installation of all components according to instructions.
Used image kubeflownotebookswg/jupyter-scipy:v1.8.0
After installation, we create a laptop based on any image and clone the repository from bitbucket with authorization.
I get an error:
After execution I get the following in the pod logs:
What did you expect to happen:
Correct cloning of the repository and further work.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kfctl version
): -kubectl version
): 1.25.3/etc/os-release
): centos 7The text was updated successfully, but these errors were encountered: