We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The docker images for the notebooks are being built at different commits
kubeflow-images-public:tensorflow-1.4.1-notebook-gpu v20180607-0d9be5e4
gcr.io/kubeflow-images-public/tensorflow-1.7.0-notebook-cpu v20180607-476e150e
Why is this happening? Why aren't they all built at a consistent commit?
If nothing else this makes updating the images in kubeform_spawner.py unwieldy.
/priority p1 because I'd like to get this fixed soon to make updating the images for the 0.2 release much more tractable.
/assign @kunmingg
The text was updated successfully, but these errors were encountered:
I guess we had timeout from gcs, so the workflow failed and retry, now they seem to be on same commit.
Sorry, something went wrong.
Close it for now till we saw it might affect user experience in future.
/close
kunmingg
No branches or pull requests
The docker images for the notebooks are being built at different commits
kubeflow-images-public:tensorflow-1.4.1-notebook-gpu
v20180607-0d9be5e4
gcr.io/kubeflow-images-public/tensorflow-1.7.0-notebook-cpu
v20180607-476e150e
Why is this happening? Why aren't they all built at a consistent commit?
If nothing else this makes updating the images in kubeform_spawner.py unwieldy.
/priority p1 because I'd like to get this fixed soon to make updating the images for the 0.2 release much more tractable.
/assign @kunmingg
The text was updated successfully, but these errors were encountered: