Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to install node 18.12.1 with the cypress/factory #851

Closed
opidhorna-dh-nf opened this issue Mar 6, 2023 · 6 comments
Closed

Unable to install node 18.12.1 with the cypress/factory #851

opidhorna-dh-nf opened this issue Mar 6, 2023 · 6 comments
Labels

Comments

@opidhorna-dh-nf
Copy link

opidhorna-dh-nf commented Mar 6, 2023

I am trying to build image cypress factory image with the following configurations:

14:08:44  Building cypress
14:08:44  Step 1/8 : ARG CHROME_VERSION='107.0.5304.121-1'
14:08:44  Step 2/8 : ARG EDGE_VERSION='100.0.1185.29-1'
14:08:44  Step 3/8 : ARG FIREFOX_VERSION='107.0'
14:08:44  Step 4/8 : ARG CYPRESS_VERSION='9.7.0'
14:08:44  Step 5/8 : ARG NODE_VERSION='18.12.1'
14:08:44  Step 6/8 : FROM cypress/factory.

The following error occurs:

14:09:04  + gpg --batch --keyserver hkps://keys.openpgp.org --recv-keys 61FC681DFB92A079F1685E77973F295594EC4689
14:09:05  gpg: key 973F295594EC4689: new key but contains no user ID - skipped
14:09:05  gpg: Total number processed: 1
14:09:05  gpg:           w/o user IDs: 1

And as a result the following command fails and image could not be build:

14:09:08  + gpg --batch --decrypt --output SHASUMS256.txt SHASUMS256.txt.asc
14:09:08  gpg: Signature made Fri Nov  4 20:12:23 2022 UTC
14:09:08  gpg:                using RSA key 61FC681DFB92A079F1685E77973F295594EC4689
14:09:08  gpg: Can't check signature: No public key

Using gpg locally I could not download the key from keyserver hkps://keys.openpgp.org:

gpg --batch --keyserver hkps://keys.openpgp.org --recv-keys 61FC681DFB92A079F1685E77973F295594EC4689
gpg: key 973F295594EC4689: new key but contains no user ID - skipped
gpg: Total number processed: 1
gpg:           w/o user IDs: 1

Buit it is okay to download it from keyservice - hkps://keyserver.ubuntu.com:

gpg --batch --keyserver hkps://keyserver.ubuntu.com --recv-keys 61FC681DFB92A079F1685E77973F295594EC4689
gpg: key 973F295594EC4689: public key "Juan José Arboleda <[email protected]>" imported
gpg: Total number processed: 1
gpg:               imported: 1
@mjhenkes mjhenkes self-assigned this Mar 6, 2023
@mjhenkes
Copy link
Member

mjhenkes commented Mar 6, 2023

I'm able to recreate this issue with just the node version set to 18.12.1

ARG NODE_VERSION='18.12.1'

FROM cypress/factory

I'm not seeing an issue with node 18.14.1 which is our default node version. For a work around would it be possible for you to use this newer version of node?

ARG CHROME_VERSION='107.0.5304.121-1'
ARG EDGE_VERSION='100.0.1185.29-1'
ARG FIREFOX_VERSION='107.0'
ARG CYPRESS_VERSION='9.7.0'

FROM cypress/factory

@mjhenkes mjhenkes added the bug label Mar 6, 2023
@mjhenkes mjhenkes removed their assignment Mar 6, 2023
@mjhenkes mjhenkes changed the title GPG self signature is broken and cypress/factory image could not be build Unable to install node 18.12.1 with the cypress/factory Mar 6, 2023
@hollyfoxx
Copy link

hollyfoxx commented Mar 14, 2023

Same thing happening here with node version 16.0.0. My team is not able to upgrade to a newer version of node, and having tried a newer version, I still get the same errors.

@mjhenkes
Copy link
Member

@hollyfoxx i was able to successfully install node 16.0.0 with:

ARG NODE_VERSION='16.0.0'

FROM cypress/factory:latest

@MikeMcC399
Copy link
Collaborator

@opidhorna-dh-nf

Are you still encountering this issue and / or do you still need Node.js 18.12.1 released Nov 3, 2022?

The Node.js 18.x LTS maintenance version is now v18.20.3 according to Node.js releases.

@MikeMcC399
Copy link
Collaborator

I can also reproduce this issue, also following the Node.js Verifying binaries documentation. To resolve, the issue would need to be addressed through https://github.com/nodejs/node/issues.

I suggest however not to follow this up because 18.12.1 is an old Node.js 18.x version and the signing process for later 18.x releases seems to be working without issue.

@MikeMcC399
Copy link
Collaborator

I'm going to close this issue as the problem with Node.js 18.12.1 does not affect currently used versions of Node.js 18.x. The workaround is to use another Node.js version.

Cypress 13.11.0 bundles Node.js 18.17.1 internally and the latest Node.js 18.x version is 18.20.3.

@MikeMcC399 MikeMcC399 closed this as not planned Won't fix, can't repro, duplicate, stale Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants