Node_14.x bionic Release' does not have a Release file

Binder
1

I get this error in ngpuller and r envirement

Get:20 http://archive.ubuntu.com/ubuntu bionic-backports/main amd64 Packages [11.3 kB]
Reading package lists...
E: The repository 'https://deb.nodesource.com/node_14.x bionic Release' does not have a Release file.
Removing intermediate container 7d13695886bc
The command '/bin/sh -c curl --silent --location --fail https://download2.rstudio.org/server/bionic/amd64/rstudio-server-1.2.5001-amd64.deb > /tmp/rstudio.deb && echo 'd33881b9ab786c09556c410e7dc477de /tmp/rstudio.deb' | md5sum -c - && apt-get update && apt install -y /tmp/rstudio.deb && rm /tmp/rstudio.deb && apt-get -qq purge && apt-get -qq clean && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100Built image, launching...
Failed to connect to event stream
2

I have the same problem.

3

Currently, repo2docker does not work on Ubuntu 20.04. If you run the repository tests on Ubuntu 20.04, they will fail.
Also, it seems that some dependencies are missing when one runs python3 -m pip install jupyter-repo2docker on Ubuntu 18.04. The tests in the repo2docker repository install some packages that are not installed together with repo2docker by running pip install.

4

It might also be a temporary problem related to this issue.

5

Thank you. i feel less alone. Is there a way to test with an olde rubunto on mybinder.org

6

It does seem to be related to the expired cert and an outdated version of ca-certificates in the buildpack-deps:bionic image. You may be able to resolve this by pulling a new version of buildpack-deps:bionic, which was updated 9 hours ago.

ca-certificates 20210119~18.04.2 apparently blacklists the expired DST Root CA X3 certificate.

In my cached version of buildpack-deps:bionic used by repo2docker, the version was 20210119~18.04.1 prior to pulling.

3 Likes
7

Now I get

Err:3 https://deb.nodesource.com/node_14.x bionic Release
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: 104.124.58.146 443]
```

I think I will add it ass issue to the bindewrhub.
8

Just to say - I’m getting the same problem - with a basic-as-possible test repo here:

@silask - did you raise an issue? Over at the the repo2docker issue, @manics said that here was the best place to discuss.

9

I was seeing this issue running repo2docker locally and updating buildpack-deps:bionic seemed to solve it. If it’s also happening on mybinder.org then maybe the old image is still cached on their servers? Sorry if I misunderstood the original issue.

10

This is the best place to discuss the general issue since it ends up affecting multiple components. For mybinder.org in particular you can follow node_14.x bionic Release Certificate verification failed · Issue #2041 · jupyterhub/mybinder.org-deploy · GitHub

2 Likes
11

From a quick read - is it fair to say that there is no easy workaround, and that we will have to wait for an update?

12

Hi all! Is anyone still experiencing problems? If so could you post on node_14.x bionic Release Certificate verification failed · Issue #2041 · jupyterhub/mybinder.org-deploy · GitHub . Thanks!

13

With Remove nodesource' nodejs by yuvipanda · Pull Request #847 · jupyterhub/repo2docker · GitHub, we no longer use node source! So this is no longer a problem :slight_smile:

1 Like