Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 20:11
    stale[bot] labeled #756
  • 20:11
    stale[bot] commented #756
  • 14:21
    TomAugspurger commented #757
  • 13:47
    jbusecke commented #757
  • Mar 27 17:33
    rabernat commented #691
  • Mar 27 17:06
    alimanfoo commented #691
  • Mar 26 19:05
    TomAugspurger commented #757
  • Mar 26 19:05
    TomAugspurger commented #757
  • Mar 26 18:59
    jbusecke commented #757
  • Mar 26 18:56
    TomAugspurger commented #757
  • Mar 26 18:45
    jbusecke commented #757
  • Mar 24 17:35
    alimanfoo commented #691
  • Mar 24 17:33
    alimanfoo commented #691
  • Mar 24 15:30
    stale[bot] closed #288
  • Mar 24 15:30
    stale[bot] commented #288
  • Mar 23 18:13
    mathildejutras commented #770
  • Mar 23 18:10
    bradyrx commented #764
  • Mar 23 17:37
    jhamman commented #769
  • Mar 23 15:00
    jbusecke commented #770
  • Mar 23 14:40
    TomAugspurger commented #770
Ryan Abernathey
@rabernat
Tom, I think you're confusing the pangeo-notebook metapackage with the pangeo-notebook Docker image
Tom Augspurger
@TomAugspurger
Yep, you’re right.
Ryan Abernathey
@rabernat
default-binder uses the pangeo/base-image docker image: https://github.com/pangeo-gallery/default-binder/blob/master/binder/Dockerfile#L1
Joe Hamman
@jhamman
Jinx!
Tim Crone
@tjcrone
Weighing in late, yes I believe pangeo-stacks-dev is the future, and the pangeo-notebook image, built from the files in https://github.com/pangeo-data/pangeo-stacks-dev/tree/master/pangeo-notebook is a good starting image.
Ryan Abernathey
@rabernat
:+1:
Tim Crone
@tjcrone
All the images that build there now, ml-notebook, pangeo-notebook, and base-notebook, build from base-image.
Ryan Abernathey
@rabernat
So one point of confusion that has emerged is the naming conflict between the pangeo-notebook metapackage and the pangeo-notebook Docker image
Tim Crone
@tjcrone
base-notebook is basically not used.
Ryan Abernathey
@rabernat
if we are going to keep this naming convention, we should put a warning in the docs about this.
Tim Crone
@tjcrone
base-image is very important. and pangeo-notebook is built directly from it.
Ryan Abernathey
@rabernat
Ok, so it sounds like pangeo-stacks-dev is ready for a little cleanup?
removing unused images, etc?
Tim Crone
@tjcrone
The base-notebook is sortof like a blank slate, minimal actual working pangeo image.
Scott Henderson
@scottyhq
I actually think base-notebook is useful - it is a minimally functional image for jupyterlab and provides a benchmark for how small we can possibly hope to have these images (before adding analysis packages like xarray, etc)
Tim Crone
@tjcrone
but it's not very useful in my opinioin.
Ryan Abernathey
@rabernat

I actually think base-notebook is useful - it is a minimally functional image for jupyterlab and provides a benchmark for how small we can possibly hope to have these images (before adding analysis packages like xarray, etc)

:+1:

Tim Crone
@tjcrone
I agree. It gives the minimal template.
Ryan Abernathey
@rabernat
ok no problem.
Tim Crone
@tjcrone
But we are not going to use it directly.
Ryan Abernathey
@rabernat
Another question: imagine I have a binder that just wants to use the pangeo-notebook image exactly as is. Does binder really need to build a new docker image from it? Or can we somehow point binder directly to the original docker image?
Scott Henderson
@scottyhq
true, and i agree there will be confusion between people wondering to use base-image or base-notebook ;)
Tim Crone
@tjcrone
and I am in the process of lobbying against metapackages and for conda-lock files, which are eminently reproducible and can all be in the stacks repo, rather than spread around several other repos.
I have not gotten traction on this idea.
Scott Henderson
@scottyhq
@rabernat Dockerfile with FROM pangeo/pangeo-notebook:2020.03.27
Ryan Abernathey
@rabernat
Right, that's what I do currently in several of my binders
Scott Henderson
@scottyhq
You just can’t add any custom config on top
Ryan Abernathey
@rabernat
what I'm asking is this: can we just use pangeo/pangeo-notebook:2020.03.27 DIRECTLY in binder, without actually building anything, since the image already exists and is ready to go?
Tim Crone
@tjcrone
Nonetheless, what @scottyhq has done with pangeo-stacks-dev is fantastic and we should focus on making it work because I think it is the future.
Ryan Abernathey
@rabernat
my understanding is that if I put a Dockerfile in my binder, repo2docker will basically copy that image to a new image
Scott Henderson
@scottyhq
Ah, right. I’ve wondered about that too. It seems like a feature of binderhub is to pull the image and then push it to the registry configured with binderhub and use that.
Ryan Abernathey
@rabernat
ok makes sense, so that would require bigger upstream changes to binderhub
Scott Henderson
@scottyhq
not sure why it can’t just pull from dockerhub directly
Joe Hamman
@jhamman
this topic would be a good one to write up on the binderhub issue tracker.
Ryan Abernathey
@rabernat
that would allow us to get more convergence between binders and regular hubs
since the nbgitpuller trick allows us to avoid packaging content together with environment
Scott Henderson
@scottyhq
thanks @tjcrone ! I think the lockfiles are key going forward as well, but the metapackage does concentrate the minimal set of things. Totally open to renaming it if necessary. Have to run to a zoom meeting. Sorry a can’t stick around longer. Great discussion.

this topic would be a good one to write up on the binderhub issue tracker.

agreed. maybe it already exists somewhere? seems like it must have come up before

Joe Hamman
@jhamman
I’ll be on board with conda-lock if we can get some traction with repo2docker (jupyter/repo2docker#670).
Ryan Abernathey
@rabernat
Yes I learned a lot. Thanks everyone.
I'm trying to manage my limited bandwidth and focus on my project of the gallery. So I will basically leave it to you binder experts to tell me the best way to launch a binder with the latest moderately full-featured pangeo environment. This can all be done via updates to https://github.com/pangeo-gallery/default-binder/
I would love to have something working quickly which we can build upon immediately, rather than waiting an indefinite period for some upstream changes
Tom Augspurger
@TomAugspurger
To “build upon immediately” I would recommend updating https://github.com/pangeo-gallery/default-binder/blob/master/binder/environment.yml to include stuff you need (xarray). And then if / when we figure out things upstream, those can be removed.
Ryan Abernathey
@rabernat
I'm going to try using the Dockerfile approach suggested above
I really can't handle another environment.yaml
:)
Tom Augspurger
@TomAugspurger
SGTM, I missed the middle part of the discussion :)
Ryan Abernathey
@rabernat
I'll make the PR
Ryan Abernathey
@rabernat
The gallery continues to get updates as things progress: http://gallery.pangeo.io/index.html