./openapi/typescript-fetch.sh ./out config will end up with a failure during the build of the docker image.
Here is the output.
Step 3/24 : RUN curl -sL https://deb.nodesource.com/setup_14.x | bash -
---> Running in 439ad1ba66ce
## Installing the NodeSource Node.js 14.x repo...
## Populating apt-get cache...
+ apt-get update
Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://deb.debian.org/debian stretch InRelease
Hit:3 http://deb.debian.org/debian stretch-updates InRelease
Hit:4 http://deb.debian.org/debian stretch Release
Reading package lists...
## Installing packages required for setup: apt-transport-https lsb-release gnupg...
+ apt-get install -y apt-transport-https lsb-release gnupg > /dev/null 2>&1
## Confirming "stretch" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_14.x/dists/stretch/Release'
## Adding the NodeSource signing key to your keyring...
+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null
## Creating apt sources list file for the NodeSource Node.js 14.x repo...
+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x stretch main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x stretch main' >> /etc/apt/sources.list.d/nodesource.list
## Running `apt-get update` for you...
+ apt-get update
Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://deb.debian.org/debian stretch InRelease
Hit:3 http://deb.debian.org/debian stretch-updates InRelease
Hit:4 http://deb.debian.org/debian stretch Release
Ign:5 https://deb.nodesource.com/node_14.x stretch InRelease
Ign:6 https://deb.nodesource.com/node_14.x stretch Release
Ign:7 https://deb.nodesource.com/node_14.x stretch/main Sources
Ign:9 https://deb.nodesource.com/node_14.x stretch/main amd64 Packages
Ign:10 https://deb.nodesource.com/node_14.x stretch/main all Packages
Ign:7 https://deb.nodesource.com/node_14.x stretch/main Sources
Ign:9 https://deb.nodesource.com/node_14.x stretch/main amd64 Packages
Ign:10 https://deb.nodesource.com/node_14.x stretch/main all Packages
Ign:7 https://deb.nodesource.com/node_14.x stretch/main Sources
Ign:9 https://deb.nodesource.com/node_14.x stretch/main amd64 Packages
Ign:10 https://deb.nodesource.com/node_14.x stretch/main all Packages
Ign:7 https://deb.nodesource.com/node_14.x stretch/main Sources
Ign:9 https://deb.nodesource.com/node_14.x stretch/main amd64 Packages
Ign:10 https://deb.nodesource.com/node_14.x stretch/main all Packages
Ign:7 https://deb.nodesource.com/node_14.x stretch/main Sources
Ign:9 https://deb.nodesource.com/node_14.x stretch/main amd64 Packages
Ign:10 https://deb.nodesource.com/node_14.x stretch/main all Packages
Err:7 https://deb.nodesource.com/node_14.x stretch/main Sources
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Ign:9 https://deb.nodesource.com/node_14.x stretch/main amd64 Packages
Ign:10 https://deb.nodesource.com/node_14.x stretch/main all Packages
Reading package lists...
W: The repository 'https://deb.nodesource.com/node_14.x stretch Release' does not have a Release file.
E: Failed to fetch https://deb.nodesource.com/node_14.x/dists/stretch/main/source/Sources server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
E: Some index files failed to download. They have been ignored, or old ones used instead.
Error executing command, exiting
The command '/bin/sh -c curl -sL https://deb.nodesource.com/setup_14.x | bash -' returned a non-zero code: 1
Looks like nodejs setup is failed due to the server certificate verification failure. I guess some changes happened recently, but the base image maven:3.5-jdk-8-slim is too old to catch up with the changes.
./openapi/typescript-fetch.sh ./out config
will end up with a failure during the build of the docker image.Here is the output.
Looks like nodejs setup is failed due to the server certificate verification failure. I guess some changes happened recently, but the base image
maven:3.5-jdk-8-slim
is too old to catch up with the changes.