Sorry to revive a concluded case ~ I like the idea a lot - I can just use Jupyter to start difference kernels under docker container instances.
However, as I wrote this, Jupyter seems to upgraded significantly and I tried to create the files in the gist, but I cannot even get the kernel shown in the dropdown list... Would there be an update to this really nice set up? thanks, Paul On Tuesday, 9 June 2015 00:30:31 UTC+8, Marius van Niekerk wrote: > > Got it working. > > Needed to make the kernel talk via 0.0.0.0 inside the container. Seems > localhost inside is not the same as outisde. > > > On Friday, 5 June 2015 10:12:49 UTC-4, Marius van Niekerk wrote: >> >> @rgbkrk: I assume once i can get it to listen and expose properly it >> should be easy enough to grab volumes from existing containers for data. >> >> So my first attempt is this guy >> >> https://gist.github.com/mariusvniekerk/09062bc8974e5d1f4af6 >> >> It spins up the container fine it seems, but the NotebookApp gets a >> Timeout. >> >> Suggestions? >> >> The custom KernelManager starts sounding like a better idea (particularly >> when it comes to shutting this thing down, since without the sockets >> seeming to respond to messages you need to docker stop these a lot). >> >> -Marius >> >> On Thursday, 4 June 2015 22:39:36 UTC-4, Min RK wrote: >>> >>> I think perhaps a custom KernelManager, rather than kernel, would be a >>> better choice here. This would let you change how connection information is >>> provided, and use the Docker Python API. >>> >>> On Thu, Jun 4, 2015 at 7:31 PM, Kyle Kelley <[email protected]> wrote: >>> >>>> Wonderful! >>>> >>>> I've been hoping to do this for some time, the notebook was an easy >>>> target for us to start with. The next pieces I'd want inside a kernel is >>>> access to my data, resources, etc. which I assume you'd have mounted in >>>> some uniform way? >>>> >>>> On Thu, Jun 4, 2015 at 7:28 PM, Thomas Kluyver <[email protected]> >>>> wrote: >>>> >>>>> On 4 June 2015 at 13:35, Marius van Niekerk <[email protected]> >>>>> wrote: >>>>> >>>>>> I assume for the connection file inside the kernel i'd have to change >>>>>> the key and signature_schema to match those mentioned in the >>>>>> {connection_file} >>>>>> >>>>>> and then make my container EXPOSE a set of static port like >>>>>> >>>>>> "stdin_port": 60000, >>>>>> "control_port": 60001, >>>>>> "hb_port": 60002, >>>>>> "shell_port": 60003, >>>>>> "iopub_port": 60004 >>>>>> >>>>>> Or do i not really need to care about the key / sig >>>>>> >>>>> >>>>> You can use static port numbers inside the container; the ports it >>>>> exposes to other things outside the container should be the ports from >>>>> the >>>>> connection file that it receives when we launch the kernel. >>>>> >>>>> If the outer system has other users, you should probably still care >>>>> about the message signing, because without it, another user could connect >>>>> to the ports exposed by the docker container and start sending messages >>>>> to >>>>> the kernel. Also, while no key means no signatures, some kernels might >>>>> not >>>>> like getting signed messages when they don't think there's a key. >>>>> >>>>> Thomas >>>>> >>>>> -- >>>>> 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/CAOvn4qiKtXjmC81fU14S23u9jH35%2BKJSp5fUw%3DjmCdoeMkSpCw%40mail.gmail.com >>>>> >>>>> <https://groups.google.com/d/msgid/jupyter/CAOvn4qiKtXjmC81fU14S23u9jH35%2BKJSp5fUw%3DjmCdoeMkSpCw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> >>>> -- >>>> Kyle Kelley (@rgbkrk <https://twitter.com/rgbkrk>; lambdaops.com, >>>> developer.rackspace.com) >>>> >>>> -- >>>> 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/CA%2BtbMaVwxSy16Zjt4mPvzA%2B%3DpdW4u0PW2mxQeqnUgCTsu2cJmw%40mail.gmail.com >>>> >>>> <https://groups.google.com/d/msgid/jupyter/CA%2BtbMaVwxSy16Zjt4mPvzA%2B%3DpdW4u0PW2mxQeqnUgCTsu2cJmw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- 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/fc1f104c-3f27-4b52-a80e-d1c27ef9fd6e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
