[Bug]: Corepack key signature error for docker image

[jamesharrisatconnexian]

Version

1.50.1-noble

Steps to reproduce

Using image: mcr.microsoft.com/playwright:v1.50.1-noble
Then running

corepack enable
corepack prepare pnpm@latest --activate

Fails with
Error: Cannot find matching keyid: {"signatures":[{"sig":"MEQCIBfxS9RKPsi46jxBHnsGYQ03mg8um110415vE6KRCzY8AiBvik66sYxJ/NyCovwJSbDuuoaYCxc7EVdFhaaciIXjTw==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],
...
at verifySignature (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:21535:47)

This is a known issue with corepack I believe and they have updated their keys but the docker image will need to be rebuilt with the latest corepack.

Expected behavior

corepack enabled and pnpm installed / available without error

Actual behavior

Using image: mcr.microsoft.com/playwright:v1.50.1-noble

corepack enable

Fails with
Error: Cannot find matching keyid: {"signatures":[{"sig":"MEQCIBfxS9RKPsi46jxBHnsGYQ03mg8um110415vE6KRCzY8AiBvik66sYxJ/NyCovwJSbDuuoaYCxc7EVdFhaaciIXjTw==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],
...
at verifySignature (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:21535:47)

Additional context

We need to install / enable npm in our CI build and use corepack to install it

This is a known issue with corepack I believe and they have updated their keys but the docker image will need to be rebuilt with the latest corepack.

Environment

OS: Ubuntu / MacOS

[dgozman]

This issue nodejs/corepack#627 suggests to run npm install -g corepack@latest. Does that work for you?

Same issue also claims that new corepack will be rolled into the latests Node.js versions. I hope that next Playwright release will pick it up and put into the docker image. I don't think we should do anything before Node.js rolls the new version.

[jamesharrisatconnexian]

Hi, yes thanks this manual npm install of corepack does work for us currently but as you say its more of a temp workaround. For our other docker containers we were able to rebuild them and this fixed the issue, so its already in all current LTS node versions and hoping as well that if playwright simply rebuilds their image on a new release it should solve the issue, just not sure when the next release is planned?