Corepack is currently busted for folks behind a proxy #28226
Unanswered
blowery
asked this question in
Request Help
Replies: 3 comments 17 replies
-
|
If corepack 0.24.1 works then you should be able to configure constraints.corepack to match that |
Beta Was this translation helpful? Give feedback.
5 replies
-
|
Hrm, didn't seem to help? I used |
Beta Was this translation helpful? Give feedback.
-
|
I was using a full image with the "global" binary source and the trace indicated that the most recent version of corepack was still being used. Switching to the non-full image (plain |
Beta Was this translation helpful? Give feedback.
-
|
Please provide more logs from prior to this error plus fix the backticks. Regarding the full image, we can roll that back to 0.24.1 if that's recommended. |
Beta Was this translation helpful? Give feedback.
-
|
Here's the full log (with a few redactions, marked) from before the error: |
Beta Was this translation helpful? Give feedback.
-
|
Seems unrelated to corepack and something to do with your environment. The error to search for is "ETXTBSY". Could be caused by eg a read only file system |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions. No logs at allIf you haven't posted any log yet, we need you to find and copy/paste the log into the issue template. Finding logs on hosted appSelect me to read instructionsIf you use the Mend Renovate app (GitHub):
Finding logs when self-hostingSelect me to read instructionsIf you're running self-hosted, run with Insufficient logsSelect me to read instructionsIf you already gave us a log, and the Renovate team said it's not enough, then follow the instructions from the No logs at all section. Formatting your logsSelect me to read instructionsPlease put your logs in a If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Found a workaround for now: setting the env var |
Beta Was this translation helpful? Give feedback.
12 replies
-
|
pnpm can be installed directly from npmjs but does Yarn v4 have a non-corepack option? https://yarnpkg.com/getting-started/install I think I'd prefer to just get corepack working if not |
Beta Was this translation helpful? Give feedback.
-
yes, will send a PR to change it for v38. should we fix it for v37 too? it's a small kind of breaking change. even if we fix corepack, it will always use the version defined in package manager field. so if that doesn't match the prepared one, then corepack will try to download the required version and fails if not possible. |
Beta Was this translation helpful? Give feedback.
-
|
Let's fix v37 too, because it's a bug if it tries to install anything at runtime. But we need to think how it works if someone turns on binarySource=global for the full image |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
We have the same problem, renovate works with our proxy in everything except corepack, is there a way change the install method? I think this is related to #28684 {
"cmd": "/bin/sh -c corepack use [email protected]",
"stderr": "",
"stdout": "Installing [email protected] in the project...\nInternal Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-9.15.4.tgz; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting\n at fetch (/opt/containerbase/tools/node/22.13.1/lib/node_modules/corepack/dist/lib/corepack.cjs:21609:11)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async fetchUrlStream (/opt/containerbase/tools/node/22.13.1/lib/node_modules/corepack/dist/lib/corepack.cjs:21639:20)\n at async download (/opt/containerbase/tools/node/22.13.1/lib/node_modules/corepack/dist/lib/corepack.cjs:21762:18)\n at async installVersion (/opt/containerbase/tools/node/22.13.1/lib/node_modules/corepack/dist/lib/corepack.cjs:21854:55)\n at async Engine.ensurePackageManager (/opt/containerbase/tools/node/22.13.1/lib/node_modules/corepack/dist/lib/corepack.cjs:22316:32)\n at async UseCommand.execute (/opt/containerbase/tools/node/22.13.1/lib/node_modules/corepack/dist/lib/corepack.cjs:22920:32)\n at async UseCommand.validateAndExecute (/opt/containerbase/tools/node/22.13.1/lib/node_modules/corepack/dist/lib/corepack.cjs:19835:22)\n at async _Cli.run (/opt/containerbase/tools/node/22.13.1/lib/node_modules/corepack/dist/lib/corepack.cjs:20772:18)\n at async Object.runMain (/opt/containerbase/tools/node/22.13.1/lib/node_modules/corepack/dist/lib/corepack.cjs:23097:19)\n",
"options": {
"cwd": "/tmp/renovate/repos/****",
"encoding": "utf-8",
"env": {
"HTTP_PROXY": "http://IP:PORT",
"HTTPS_PROXY": "http://IP:PORT",
"NO_PROXY": "127.0.0.1,localhost",
"http_proxy": "http://IP:PORT",
"https_proxy": "http://IP:PORT",
"no_proxy": "127.0.0.1,localhost",
"HOME": "/home/ubuntu",
"PATH": "/home/ubuntu/.local/bin:/home/ubuntu/bin:/home/ubuntu/.local/bin:/home/ubuntu/bin:/home/ubuntu/.local/bin:/home/ubuntu/bin:/home/ubuntu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"LC_ALL": "C.UTF-8",
"LANG": "C.UTF-8"
},
"maxBuffer": 10485760,
"timeout": 900000
},
"exitCode": 1,
"name": "ExecError",
"message": "Command failed: corepack use [email protected]\n",
"stack": "ExecError: Command failed: corepack use [email protected]\n\n at ChildProcess.<anonymous> (/usr/local/renovate/lib/util/exec/common.ts:101:11)\n at ChildProcess.emit (node:events:536:35)\n at ChildProcess.emit (node:domain:489:12)\n at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12)"
} |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
Other
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Github Enterprise, via Docker and renovate:37
Please tell us more about your question or problem
We noticed that recently corepack installs of yarn were failing while trying to download yarn from the global NPM registry. After a bunch of debugging, it appears to be this bug in corepack: nodejs/corepack#417
Just wanted to highlight this issue, as anyone who's self-hosting and behind a proxy and on something that requires corepack is probably stuck.
Beta Was this translation helpful? Give feedback.
All reactions