-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Initial stacks #1
Conversation
&& apt-get clean | ||
|
||
ENV CONDA_DIR /opt/conda | ||
ENV NB_USER jovyan |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, cool, I'm glad you adopted a non-root convention here as well.
We're going to end up getting reports about file permissions during mounting but we'll cross that bridge (again) later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. I think this is where additional doc or helper scripts can help.
These READMEs and setups are really great @parente. 👍 Very thorough and well thought out. |
I've force pushed to condense the commits and removed the mistaken header. |
Cool, I think these look good. |
Make python package
Tickets/dm 11417
Tickets/dm 11937
I'm submitting this PR not expecting it to get merged as-is, but as a strawman for discussion. It contains:
minimal-notebook
which acts as a base image or a lightweight notebook environment in which the user can use conda to install everythingscipy-notebook
for a Python 2 and 3 stackr-notebook
for an R stackMost package versions are pegged to allow patch level increases only to avoid breakage across Docker builds. (I've learned this the hard way.)
If this is inline with what people are thinking for this repo, follow-ons might be:
all-spark-notebook
(Scala, Python, R w/ Spark 1.4.x plus Yarn and Mesos connectivity preconfigured)data-science-notebook
(needs a better name) with Python, R, Julia, Scala, Spark (Brian's request)julia-notebook
maybeI don't want to go too crazy with a ton of different options yet until we know if less is more or not.
Ideally, once these (or alternatives) are merged, the jupyter account on Docker Hub can be configured to build the minimal-notebook stack on commit and webhook build the other stacks on build of that base.