Simple Pangeo binder spin up failing on provision

[scollis]

Very simple set up (no dockerfile etc). failing on what looks like the provision of the container

Removing intermediate container 9f3c9d91d6b1
 ---> d9988d005870
Step 14/53 : RUN wget --quiet -O - https://deb.nodesource.com/gpgkey/nodesource.gpg.key |  apt-key add - &&     DISTRO="bionic" &&     echo "deb https://deb.nodesource.com/node_10.x $DISTRO main" >> /etc/apt/sources.list.d/nodesource.list &&     echo "deb-src https://deb.nodesource.com/node_10.x $DISTRO main" >> /etc/apt/sources.list.d/nodesource.list
 ---> Running in 2a0b7819c6f7
Warning: apt-key output should not be parsed (stdout is not a terminal)
OK
Removing intermediate container 2a0b7819c6f7
 ---> 4d996a72d6dc
Step 15/53 : RUN apt-get -qq update &&     apt-get -qq install --yes --no-install-recommends        less        nodejs        unzip        > /dev/null &&     apt-get -qq purge &&     apt-get -qq clean &&     rm -rf /var/lib/apt/lists/*
 ---> Running in 7fcf312c303e
E: The repository 'https://deb.nodesource.com/node_10.x bionic Release' does not have a Release file.
Removing intermediate container 7fcf312c303e
The command '/bin/sh -c apt-get -qq update &&     apt-get -qq install --yes --no-install-recommends        less        nodejs        unzip        > /dev/null &&     apt-get -qq purge &&     apt-get -qq clean &&     rm -rf /var/lib/apt/lists/*' returned a non-zerocode: 100

"Normal" binder works.

here is the repo https://github.com/ARM-Development/PyART-Training

[rabernat]

Thanks for reporting Scott.

[choldgraf]

One quick thought, I wonder if this could be resolved by updating the build image for repo2docker? Looking at the config, it seems like it hasn't been updated in about 12 months: https://github.com/pangeo-data/pangeo-binder/blame/2eda78b78a9aa60f36f296337f3767ace55bbcf9/pangeo-binder/values.yaml#L7

Here's where the latest build images are for repo2docker (now on quay.io): https://quay.io/repository/jupyterhub/repo2docker?tab=tags

I am curious if @yuvipanda thinks that something like this would potentially resolve this issue. @scottyhq when the build image has been updated on this binderhub in the past, has it caused issues?

[choldgraf]

A note that some kinds of similar reports are in mybinder.org as well: https://github.com/jupyterhub/mybinder.org-deploy/issues/2041

and discussed here as well: https://discourse.jupyter.org/t/node-14-x-bionic-release-does-not-have-a-release-file/11048/6

and seems node folks know about it as well, if in fact node is the core problem: https://github.com/nodesource/distributions/issues/1266#issuecomment-931448879

[scottyhq]

@scottyhq when the build image has been updated on this binderhub in the past, has it caused issues?

Not really sure... In the past we tried to keep versions in sync with whatever mybinder.org was using https://github.com/jupyterhub/mybinder.org-deploy , but obviously this repo has not been getting many updates this last year

Thanks for the links to relevant issues. Seems like we will have to bump the build image or clear cache to resolve. But in the short term if people are building off the pangeo Dockerfile things still work. See: https://github.com/pangeo-data/pangeo-binder-template