-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Pipeline notebook samples : "Install Pipeline SDK " error #610
Comments
Maybe there are some network problem between your jupyter pod and |
@xiaozhouX how can I check jupyter pod ? But I find it in my (ns kubeflow) get pod have problem in
Get logs :
|
Duplicate of #603 |
+1 Having the same problem. v0.4.0 |
@hamedhsn what problem did you see in v0.4.0 it looks like there are multiple issues mentioned in this issues and some of them are fixed. |
exactly like what @yylin1 reported..pods related to pipelines are all up except |
@hamedhsn You are new deploy on v0.4.0 ? get pod same problem I can try to change the version for v0.4.0. (testing) |
yes, it is a new deployment(testing 0.4.0) and getting the same error. |
The load sample issue should not lead to the SDK installation error. Are you still having problems in installing the SDK in the notebook? If so, "pip3 install https://storage.googleapis.com/ml-pipeline/release/0.1.4/kfp.tar.gz --upgrade" should work fine in any networked computers and you could try running this in your own machine to see if it works. My guess is that the SDK installation problem is mostly about network failure. |
@gaoning777 I can install the pip package with no problem. |
Resolving since inactive for 2 months. Please reopen if needed. |
I think I'm hitting a similar issue, seeing
|
* Create a flask server to provide information about the auto-deploymens
I‘m trying to test sample for "KubeFlow Pipeline Using TFX OSS Components", but have error for
Collecting https://storage.googleapis.com/ml-pipeline/release/0.1.4/kfp.tar.gz
.Environment:
JupyterHub Spawner :
The text was updated successfully, but these errors were encountered: