Corepack runs into an internal error with newest iron node image [Proxy issue] #447

Activity

1. Chreggii

   changed the title [-]Corepack runs into an internal error with node version node:iron@sha256:04223c46b1b8998bccbb6e6208dbed8344916ffc1be9f446109ffcb9629ad791[/-] [+]Corepack runs into an internal error with newest iron node version[/+] on Apr 2, 2024
2. Chreggii commented on Apr 8, 2024

   

   Chreggii

   on Apr 8, 2024

   Last edited by Chreggii

   Author

   More actions

   It seems to be a proxy issue.

   For reproducing the issue run the following code in a gitlab-ci pipeline (new node image):

   stages:
     - build
   
   build:
     stage: build
     image: node:iron@sha256:b73550fae550a1385e56500f4d95545f4808439828786e9bff9913e6a57989dc
     before_script:
       - corepack enable
       - HTTPS_PROXY=$CODE_PROXY corepack prepare pnpm@latest-8 --activate
       - pnpm config set store-dir .pnpm-store
     script:
       - HTTPS_PROXY=$CODE_PROXY pnpm install # install dependencies
     cache:
       key:
         files:
           - pnpm-lock.yaml
       paths:
         - .pnpm-store
   

   With the previous node image everything worked fine:

   stages:
     - build
   
   build:
     stage: build
     image: node:iron@sha256:894c91653e564b9ba29400e6e1675bbcbc667158c1706c655dd4ccf84d0f54e8
     before_script:
       - corepack enable
       - HTTPS_PROXY=$CODE_PROXY corepack prepare pnpm@latest-8 --activate
       - pnpm config set store-dir .pnpm-store
     script:
       - HTTPS_PROXY=$CODE_PROXY pnpm install # install dependencies
     cache:
       key:
         files:
           - pnpm-lock.yaml
       paths:
         - .pnpm-store
   
3. Chreggii

   changed the title [-]Corepack runs into an internal error with newest iron node version[/-] [+]Corepack runs into an internal error with newest iron node image [Proxy issue][/+] on Apr 8, 2024
4. nan-mu commented on Apr 8, 2024

   

   nan-mu

   on Apr 8, 2024

   More actions

   Same question and I have gave up. Corepack should just fit with system proxy

   I would like to suggest that corepack should not be the only way to set up a package management tool, which a lot of tools are doing now. Both Windows and Linux systems have their own package management tools and they have performed their jobs well for a long time. Corepack undoubtedly adds a lot of learning costs.
5. ertl commented on Apr 10, 2024

   

   ertl

   on Apr 10, 2024

   More actions

   Same Problem here. Any Workarounds?
6. aduh95 commented on Apr 10, 2024

   

   aduh95

   on Apr 10, 2024

   Contributor

   More actions

   Hopefully this should be fixed by #451. In the mean time, downgrading to corepack@0.24.1 might be a workaround.

   👍React with 👍1Reacted by ertl