Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error installing node.js: The Node.js binary could not be verified.

See original GitHub issue

When I run the build I receive the following error:

Sending build context to Docker daemon     75MB
Step 1/15 : FROM launcher.gcr.io/google/nodejs
 ---> d8132d024114
Step 2/15 : RUN install_node v12.16.2
 ---> Running in 80fefff9837f
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 22.0M  100 22.0M    0     0  8969k      0  0:00:02  0:00:02 --:--:-- 8969k
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  4029  100  4029    0     0  11964      0 --:--:-- --:--:-- --:--:-- 11991
gpg: Signature made Wed Apr 8 19:22:22 2020 UTC using RSA key ID 5599653C gpg: Can't check signature: public key not found
The Node.js binary could not be verified.
This means it may not be an officially released Node.js binary
or may have been tampered with.

Aborting the installation.

The installation can be forced using the --ignore-verification-failure
flag. However, it is strongly recommended that you install a version
of Node.js that can be verified.

Node installation failed: /opt/gcp/runtime/bootstrap_node exited with a non-zero exit code: 1
The command '/bin/sh -c install_node v12.16.2' returned a non-zero code: 1

I have the following configuration:

# Dockerfile extending the generic Node image with application files for a
# single application.
FROM launcher.gcr.io/google/nodejs

# Check to see if the the version included in the base runtime satisfies
# '>=8.12.0', if not then do an npm install of the latest available
# version that satisfies it.
# RUN /usr/local/bin/install_node '>=12.13.0'
RUN install_node v12.16.2

When I do what is suggested it installs the node:

RUN install_node v12.16.2 --ignore-verification-failure

but clearly there is a problem somewhere.

Issue Analytics

State:
Created 3 years ago
Reactions:6
Comments:67 (6 by maintainers)

Top GitHub Comments

13reactions

alexnaultcommented, May 13, 2021

I confirm: Node 14.17.0 is having that same issue. Note: Node 14.16.0 works fine.

6reactions

BethGriggscommented, Oct 13, 2021

The issue is possibly that the KEYS file in this repository has not been updated to contain @danielleadams’s new key (updated in January, https://github.com/nodejs/node/pull/36793).

The Node.js project has recently started to maintain https://github.com/nodejs/release-keys/tree/main/keys as a source of truth for our release keys, which might be a useful resource for keeping this repository in sync with Node.js key updates.

Top Results From Across the Web

App engine deployment down with "The Node.js binary could ...

However, it is strongly recommended that you install a version Step #1: of Node.js that can be verified. Step #1: Step #1: Node...

google app engine nodejs deployment error - Server Fault

As per the documentation, this occurs when the associated binary for the downloaded Node.js version you are using is not an officially ...

How to resolve 'node' is not recognized as an internal or ...

How to resolve 'node' is not recognized as an internal or external command error after installing Node.js ? · Open the Environment Variables ......

Missing GPG key for node js Flex environement - Issue Tracker

Step #1: This means it may not be an officially released Node.js binary Step ... The installation can be forced using the --ignore-verification-failure...

How to Install Node.js on a Mac - Webucator

The first thing you should do is check to see if you have a version of Node.js already installed. To do that: Open...