-
Notifications
You must be signed in to change notification settings - Fork 391
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
BinderHub setup on Azure timesout when trying to contact docker registry #809
Comments
The bit where the error happened is trying to talk to the docker registry you configured. In this case it timed out which sounds like a network problem. It isn't even at the level where it tried the credentials and then failed. Maybe a firewall issue or docker hub (are you using docker hub?)being down/unreachable? Could you also post your |
Could it be this #811? |
Thanks for looking into this. Yeah, I don't think I have |
I don't have any good ideas :-( Maybe worth moving this discussion to http://discourse.jupyter.org/ in the hopes that it gets more eyes/fresh eyes on it? I'll close this under the assumption that we either move the discussion or that it has somehow solved itself/become low priority. We can reopen this when there is new info/ideas. |
I've run into the same problem. Using kubectl logs I get the following backtrace. [I 190601 09:03:19 repoproviders:447] Using cached ref for https://api.github.com/repos/opesci/devito/commits/binder: dd2a5f878159bcc2b2523c67384fdc01c18a2d68 |
check or remove token_url config item: |
When following zero to binderhub instructions using Azure, the following command:-
Produced this error message:-
We managed to fix this using this issue. However, when trying to use my own binderhub with an example repo I get an "Internal server error". I have checked by dockerhub username and password and they are correct.
I can look at the log files with the command
and the following error is seen
The text was updated successfully, but these errors were encountered: