Skip to content
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

Custom deployment to GCP: Failed to start your server. #337

Closed
samanvp opened this issue Jul 16, 2018 · 6 comments
Closed

Custom deployment to GCP: Failed to start your server. #337

samanvp opened this issue Jul 16, 2018 · 6 comments
Labels

Comments

@samanvp
Copy link

samanvp commented Jul 16, 2018

I followed guideline to bring up a custom deployment to GCP. Everything goes as expected (BTW, thanks for clear and detailed steps) until I authenticate and try to "Start my Server". It shows the Your server is starting up. You will be redirected automatically when it's ready for you. for a few minutes and then fails with this error message:

500 : Internal Server Error
Failed to start your server. Please contact admin.
You can try restarting your server from the home page.

In GCP Console I see the following error:

Error: ImagePullBackOff
Failed to pull image "pangeo/notebook:ce2f7f5": rpc error: code = Unknown desc = Error response from daemon: manifest for pangeo/notebook:ce2f7f5 not found
Error: ErrImagePull	Failed
pulling image "pangeo/notebook:ce2f7f5"

I am wondering what might be causing this?

Thanks for your help.

@jgerardsimcock
Copy link

Docker hub tags for pangeo don't show that commit. What about deploying from a different tag?

@samanvp
Copy link
Author

samanvp commented Jul 16, 2018

Thanks for your quick respond.
How can I change that tag? I cannot see any setting in jupyter_config.yaml for changing it?

As a side note, in your guideline there is a inconsistency in yaml files name: you have both jupyter_config.yaml and jupyter-config.yaml

@samanvp
Copy link
Author

samanvp commented Jul 16, 2018

I found it:
In Upgrade Cluster section one can update the helm chart version. For some reason some the versions are missing the corresponding Docker hub tags for pangeo.

Make sure select a version that also has a tag.

@kaipak
Copy link

kaipak commented Jul 19, 2018

I am also running into issues with the latest Helm chart releases and had to revert to earlier versions. I see that a new release just came out (v0.1.1-2d5c8b4) and so far, that seems to start up without issue.

@stale
Copy link

stale bot commented Sep 17, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Sep 17, 2018
@stale
Copy link

stale bot commented Sep 24, 2018

This issue has been automatically closed because it had not seen recent activity. The issue can always be reopened at a later date.

@stale stale bot closed this as completed Sep 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants