Pangeo Notebook / nbgitpuller incompatibility

[cisaacstern]

We currently pin to

sandbox/binder/Dockerfile

Line 1 in a47d7ff

FROM pangeo/pangeo-notebook:2021.12.02

for compatibility with nbgitpuller as noted in #6.

Ideally, we could re-pin to the latest notebook image at the time of the latest pangeo-forge-recipes release.

If this is not possible, we should be careful that notebook versions used by the eventual solution to pangeo-forge/pangeo-forge-bakery-images#7 don't introduce incompatibilities between the Sandbox and bakery (i.e. worker) images.

[cisaacstern]

Noting that I've just had to revert #10 because the build appeared to error out due to what looked like a version clash between some requirement of pangeo-forge-recipes==0.9.0 and some underlying dependencies in the old pangeo notebook version we're pinning (due to the incompatibility of later notebook versions with nbgitpuller).

I'm working relatively quickly at the moment and didn't capture a full traceback or synthesize this into a minimal reproducer, but when I (or anyone) gets a moment, it would be good to do that and chime in with some recent experience on the upstream tracker: pangeo-data/pangeo-docker-images#272

[rabernat]

One short-term workaround is to just explicitly specify an environment in the environment.yaml in the binder branch and forget about building on pangeo-docker-images.

[cisaacstern]

One short-term workaround is to just explicitly specify an environment in the environment.yaml in the binder branch and forget about building on pangeo-docker-images.

Thanks for the suggestion. Yes, I may do this tonight, just to have a more reliably buildable environment with the latest pangeo-forge-recipes for tomorrow's tutorial.

[cisaacstern]

Anecdotally, it appears that the latest pangeo-docker-images release does work with nbgitpuller.

I ran through a few other ideas (environment.yml, etc.) for the binder branch environment, and then on a whim tried just

FROM pangeo/pangeo-notebook:latest

which worked 🎉 .

When I get a moment later this week, I'll follow up on the upstream thread.