These are chat archives for ipython/ipython

10th
Jul 2015
Peter Parente
@parente
Jul 10 2015 13:08
i'm considering putting together a Dockerfile that preconfigures jupyter notebook, Spark in local mode, and both Python and Scala kernels to work with it. i've seen a few people ask for this in this channel and elsewhere.
if i do it, it would be great to have it up on docker hub under jupyter/notebook-with-spark or something. but i don't see a generic place in the jupyter/* github repos to contribute such dockerfiles.
does it makes sense to open up a new github.com/jupyter/dockerfiles or jupyter/containers or ... where such things could live for dockerhub to pull and automatically build?
Min RK
@minrk
Jul 10 2015 13:52
@parente we have notebook docker files in https://github.com/jupyter/docker-demo-images
Peter Parente
@parente
Jul 10 2015 15:22
@minrk the title threw me off that it was for try.jupyter.org and tmpnb.org only. but if you're open to having that be a general purpose repo for dockerfiles that package jupyter+extras for people to quickly pull down from dockerhub to try out, i'm fine with that.
i'm envisioning notebook+spark, notebook+scipy-stack, notebook+r-stack, ... as nice offerings for folks to just "docker run jupyter/notebook-<some stack>" to get working and/or try things out
Min RK
@minrk
Jul 10 2015 15:29
If it's more of a dumping ground of examples, perhaps a new repo makes sense. For now, you can go ahead and make a PR on that repo, and we can move it somewhere else if need be.
Răzvan Cosmin Rădulescu
@razvanc-r
Jul 10 2015 15:37
i'm just checking this irc connection gitter thing...
Peter Parente
@parente
Jul 10 2015 15:38
ok, cool, will do.
Peter Parente
@parente
Jul 10 2015 15:44
given how docker hub works and can automatically rebuild images on github webhooks and other image rebuilds, i'm hoping that if there's a repo for dockerfiles like these to live, they can autobuild on change and show up on docker hub as jupyter/* as prepackaged stacks.
maybe @rgbkrk has some thoughts too
Min RK
@minrk
Jul 10 2015 16:11
@parente yes, we are already doing that for other dockerfiles in that repo.
Peter Parente
@parente
Jul 10 2015 16:11
ok, sweet
Min RK
@minrk
Jul 10 2015 16:12
I think we likely want a spark demo on try.jupyter as well, so it may be integrated to the existing demo images as well.
Peter Parente
@parente
Jul 10 2015 16:19
makes sense. i will start from the same base that's in the current repo so it can be.
Kyle Kelley
@rgbkrk
Jul 10 2015 18:09
Hi @parente !
I'd certainly be a fan of those
Peter Parente
@parente
Jul 10 2015 18:09
hi @rgbkrk
Kyle Kelley
@rgbkrk
Jul 10 2015 18:09
I'm at SciPy, been busy with people in person here
Peter Parente
@parente
Jul 10 2015 18:09
that's more important. no worries :)
Kyle Kelley
@rgbkrk
Jul 10 2015 18:09
Sorry I wasn't available earlier
Okay!
Peter Parente
@parente
Jul 10 2015 18:11
i've got a couple approaches in progress. 1.plugging the spark stuff into the existing try.jupyter image. 2. re-orging the repo a bit so that it can host dockerfiles for images that folks can pull and run elsewhere, not just try.jupyter.
i'll open an issue and submit PRs so we can carry on the discussion there when there's something to point at
Kyle Kelley
@rgbkrk
Jul 10 2015 18:11
Yeah, we need to change our image names too
the demo image (current one) should be named jupyter/tmpnb-demo or something
Peter Parente
@parente
Jul 10 2015 18:12
yea. one of those two hard CS problems. naming.
agreed. i consider what i'm doing right now a stab at a first pass. i'm sure we'll go back and forth on it a few times to get it done.
Kyle Kelley
@rgbkrk
Jul 10 2015 18:12
https://github.com/ipython/docker-notebook was our place for stacks of stuff originally
Yeah
Sounds great!
Too bad you're not here at SciPy to collab
I'm currently in the Jupyter Education BoF
Peter Parente
@parente
Jul 10 2015 18:20
yea. i'm hoping to get more involved.