[IPython-dev] Unable to start Jupityr on Docker using "Quick start" instructions
rgbkrk at gmail.com
Tue Oct 28 18:04:13 EDT 2014
Yup, the maximum number of containers is controlled by the pool size
parameter (and the upper memory limit is the mem-limit param).
That is pretty strange behavior that I can replicate for the right set of
parameters. My hunch is that it's related to the initial heartbeat of the
culling/spawnpool service, as lightly raised in
On Tue, Oct 28, 2014 at 7:30 PM, roalexan <roalexan at microsoft.com> wrote:
> So, having looked at the code (in particular orchestrate.py) it is clear
> tmpnb has a background process that will "pre-launch a set number of
> containers". I think that the number of containers is controlled by the
> /pool-size/ parameter (and the upper memory limit per container is set by
> the /mem-limit/ parameter).
> Having said that, I would expect going to http://MYHOST.cloudapp.net:8000
> would open up a notebook using one of the pre-allocated containers. What it
> actually does is redirect me to: http://MYHOST.cloudapp.net:8000/spawn/,
> which fails with an error (...It looks like we're full up. Every single
> container is in use right now!).
> I can manually get it to work by looking in the log file of
> jupyter/tmpnb:latest to find a valid user name of one of the containers to
> construct a URL like,
> http://MYHOST.cloudapp.net:8000/user-dH5GL6B4B0pN/tree, but what I really
> need is the correct URL entry point that I should be using. Can somebody
> please help me with this?
> View this message in context:
> Sent from the IPython - Development mailing list archive at Nabble.com.
> IPython-dev mailing list
> IPython-dev at scipy.org
Kyle Kelley (@rgbkrk <https://twitter.com/rgbkrk>; http://lambdaops.com)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPython-dev