Skip to content
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

Merged
merged 1 commit into from
Jul 22, 2015
Merged

Initial stacks #1

merged 1 commit into from
Jul 22, 2015

Conversation

parente
Copy link
Member

@parente parente commented Jul 21, 2015

I'm submitting this PR not expecting it to get merged as-is, but as a strawman for discussion. It contains:

  1. minimal-notebook which acts as a base image or a lightweight notebook environment in which the user can use conda to install everything
  2. scipy-notebook for a Python 2 and 3 stack
  3. r-notebook for an R stack
  4. READMEs for each

Most 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:

  1. all-spark-notebook (Scala, Python, R w/ Spark 1.4.x plus Yarn and Mesos connectivity preconfigured)
  2. data-science-notebook (needs a better name) with Python, R, Julia, Scala, Spark (Brian's request)
  3. julia-notebook maybe

I 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.

&& apt-get clean

ENV CONDA_DIR /opt/conda
ENV NB_USER jovyan
Copy link
Member

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.

Copy link
Member Author

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.

@rgbkrk
Copy link
Member

rgbkrk commented Jul 21, 2015

These READMEs and setups are really great @parente. 👍 Very thorough and well thought out.

@parente
Copy link
Member Author

parente commented Jul 21, 2015

I've force pushed to condense the commits and removed the mistaken header.

@rgbkrk
Copy link
Member

rgbkrk commented Jul 22, 2015

Cool, I think these look good.

rgbkrk added a commit that referenced this pull request Jul 22, 2015
@rgbkrk rgbkrk merged commit ac2be95 into jupyter:master Jul 22, 2015
@parente parente mentioned this pull request Aug 26, 2015
@parente parente mentioned this pull request Mar 7, 2016
@parente parente deleted the initial-stacks branch March 26, 2018 01:20
rochaporto pushed a commit to rochaporto/docker-stacks that referenced this pull request Jan 23, 2019
rochaporto pushed a commit to rochaporto/docker-stacks that referenced this pull request Jan 23, 2019
rochaporto pushed a commit to rochaporto/docker-stacks that referenced this pull request Jan 23, 2019
mathbunnyru pushed a commit that referenced this pull request Feb 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants