Commit 296a819
authored
fix Docker build (#553)
We're a bit behind on pnpm versions and this causes issues with newer
node installs and corepack. The issue is related to verifying the PNPM
tarball signature, and it's failing because the signature in the TUF
metadata cannot be validated—likely due to a key mismatch or
expired/incomplete keyring used by Corepack:
```
Internal Error: Cannot find matching keyid: {"signatures":[{"sig":"MEUCIQDH6Kte1awtFvRUVsKWHtRaKuryH/0lm0Wswd29C+NdWAIgMxcudJ1cOlbnCh3oiFLkrQLua0vp6H+mGvycpY4TzxM=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"keys":[{"expires":null,"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","keytype":"ecdsa-sha2-nistp256"
```
To work arround this I'm installing a pinned version of pnpm through
corepack:
```
RUN corepack enable && corepack prepare [email protected] --activate
```
And removed the please use pnpm check script, its no longer needed.
People can figure it out or they should read the readme.3 files changed
+1
-15
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
12 | | - | |
| 12 | + | |
13 | 13 | | |
14 | 14 | | |
15 | 15 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
14 | 14 | | |
15 | 15 | | |
16 | 16 | | |
17 | | - | |
18 | 17 | | |
19 | 18 | | |
20 | 19 | | |
| |||
This file was deleted.
0 commit comments