Further oddness (for anyone who is still following along...).
I suddenly realize the error is about "jupyter/singleuser", when the
dockerspawner install instructions were all about "jupyterhub/singleuser".
Suddenly my hub is trying to work with jupyter/singleuser where before it
was using jupyterhub/singleuser. Now I feel more lost than ever!
I tried building the jupyter/singleuser image just to see what would
happen, but that dies immediately with the following docker log:
[FATAL tini (5)] Executing child process
'/usr/local/bin/start-singleuser.sh' failed: 'No such file or directory'
So.. somehow I went from a situation where dockerspawner was launching a
jupyterhub/singleuser image but there was a redirect loop, to a situation
where it doesn't even try to launch that image, but launches the
jupyter/singleuser image instead.
I must have done something really stupid..
On Sunday, May 7, 2017 at 10:28:47 AM UTC-4, Eric Dennison wrote:
>
> Thanks - that gave me some ideas to try.
>
> Now the situation has gotten worse, though.. :)
>
> I went in to docker and removed the existing containers, and even the
> jupyter/singleuser image, rebuilt the image and restarted. But now I am
> receiving 500 Internal Server Error and the traceback informs me that:
>
> docker.errors.ImageNotFound: 404 Client Error: Not Found ("No such image:
> jupyter/singleuser:latest")
>
> which is clearly nonsense because it exists in the docker image list. I
> can start it manually with `docker run`
>
>
>
> On Sunday, May 7, 2017 at 1:27:31 AM UTC-4, Adam Thornton wrote:
>>
>> When I get the too many redirects with Kubespawner it means that the back
>> end is running but doesn't have the token the front end is expecting. Make
>> sure you are passing the right API token to the spawned container. I
>> haven't used Dockerspawner though, so this guess could be completely wrong.
>
>
--
You received this message because you are subscribed to the Google Groups
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jupyter/8f57d78a-7abd-495d-926a-9de0d59e60b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
