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

Cannot bypass "Corepack is about to download" prompt #550

Open
moltar opened this issue Aug 21, 2024 · 2 comments
Open

Cannot bypass "Corepack is about to download" prompt #550

moltar opened this issue Aug 21, 2024 · 2 comments

Comments

@moltar
Copy link

moltar commented Aug 21, 2024

I'm trying to run corepack inside devcontainers, in a postCreateCommand.

I've upgraded corepack to latest:

npm install --yes --global corepack@latest

Then run:

corepack -v && COREPACK_ENABLE_DOWNLOAD_PROMPT=0 corepack enable

The output I get:

0.29.3
! Corepack is about to download https://registry.npmjs.org/pnpm/-/pnpm-9.7.1.tgz
? Do you want to continue? [Y/n] 

I've tried setting CI too, but also does not work.

Any clues?

@GDWR
Copy link

GDWR commented Aug 23, 2024

I just ran into this, although setting that environment variable worked fine for me.
I did this in the Dockerfile. Below is an example, and my full Docker below that if useful.

FROM #...

# ...

RUN corepack enable && corepack install --global [email protected]
ENV COREPACK_ENABLE_DOWNLOAD_PROMPT=0
Full Dockerfile
FROM mcr.microsoft.com/devcontainers/base:ubuntu-24.04

# Install node
# https://nodejs.org/en/download/prebuilt-binaries
ARG NODE_VERSION="20.17.0"
ARG NODE_CHECKSUM="a24db3dcd151a52e75965dba04cf1b3cd579ff30d6e0af9da1aede4d0f17486b"
RUN wget --https-only "https://nodejs.org/dist/v${NODE_VERSION}/node-v${NODE_VERSION}-linux-x64.tar.xz" -O /tmp/node.tar.xz && \
    sha256sum /tmp/node.tar.xz | grep "${NODE_CHECKSUM}" && \
    tar -C /usr/local -xf /tmp/node.tar.xz --strip-components=1 --exclude="CHANGELOG.md" --exclude="LICENSE" --exclude="README.md" && \
    rm /tmp/node.tar.xz && \
    corepack enable && \
    corepack install --global [email protected]
ENV COREPACK_ENABLE_DOWNLOAD_PROMPT=0

jmikedupont2 pushed a commit to meta-introspector/cloud-deployment-eliza that referenced this issue Jan 28, 2025
adding bugfix from

nodejs/corepack#550
RUN corepack enable && corepack install --global [email protected]
ENV COREPACK_ENABLE_DOWNLOAD_PROMPT=0
jmikedupont2 pushed a commit to meta-introspector/cloud-deployment-eliza that referenced this issue Feb 10, 2025
parent c9d4411
author mike dupont <[email protected]> 1736342650 -0500
committer mike dupont <[email protected]> 1736549491 -0500

rebase and squash

parent 1d5d74a
author mike dupont <[email protected]> 1736342650 -0500
committer mike dupont <[email protected]> 1736435015 -0500

parent 1d5d74a
author mike dupont <[email protected]> 1736342650 -0500
committer mike dupont <[email protected]> 1736435001 -0500

starting on the slimdown

now it is building

lint fix

Update pnpm-lockfile-check.yml

Update pr.yaml

Update integrationTests.yaml

Update image.yaml

Update image.yaml

Update pnpm-lockfile-check.yml

Update smoke-tests.yml

Update greetings.yml

Update image.yaml

Update image.yaml

removing new packages

adding docker hub

update

switching to our org

now running locally

update

parent de8a422f0f391c7612ba0f2776ca1a00b69ba04e
author mike dupont <[email protected]> 1736553320 -0500
committer mike dupont <[email protected]> 1739207256 -0500

merge

parent de8a422f0f391c7612ba0f2776ca1a00b69ba04e
author mike dupont <[email protected]> 1736553320 -0500
committer mike dupont <[email protected]> 1739207041 -0500

merge

parent de8a422f0f391c7612ba0f2776ca1a00b69ba04e
author mike dupont <[email protected]> 1736553320 -0500
committer mike dupont <[email protected]> 1739207003 -0500

merge

parent de8a422f0f391c7612ba0f2776ca1a00b69ba04e
author mike dupont <[email protected]> 1736553320 -0500
committer mike dupont <[email protected]> 1739206252 -0500

parent de8a422f0f391c7612ba0f2776ca1a00b69ba04e
author mike dupont <[email protected]> 1736553320 -0500
committer mike dupont <[email protected]> 1739206086 -0500

parent de8a422f0f391c7612ba0f2776ca1a00b69ba04e
author mike dupont <[email protected]> 1736553320 -0500
committer mike dupont <[email protected]> 1739206065 -0500

Now responding locally, it shows akash

adding systemd and start script

Update README.md

first draft untested of sdk with no boot yet

readme

update readme and bootscript

adding curl to the dockerfile

now booting into chatgpt

adding the docker compose .env example

working locally

conditions:
1. the volume has to be new
2. the mount has to be correct
3. docker populates the new volume with the existing data.

adding FIXME for values to change

adding platforms

plaforms

lets get this build working

remove install

try the default node image

try again

changing targets

change tag

node

a new try and removing forked modules

run local docker helper

runlocaldocker

fixing bad tag

strace

wip

a second copy

adding

adding my local files to git ignore

falsy ignored

install

fix

fix

update

fix

this might just work

now this might work

W00T! its running :)

update vec

hold for jump

adding notes from demo

how to set secure parameters in ssm

first version of adding the new variables for using nvidia

point tine at nvidia free tier api

update

fix

adding new variables

update url

groq

bugfix rundocker

typo in name

remove things causing us to wait

workaround

now we commit groq patched

fix the char path

/opt/agent is for the docker
/app/agent is where the application is run from

Working on twitter

adding in 3 new variables
username, password and email

removing hard coded secrets and replacing with generic loop

adding verbose

splitting

rundocker

rundocker

get secrets

splitting the get variables into a new file

quoting parameters

escape with double quotes

update

update docs on how to test twitter

not quoting

the variables are messed up

first results of running bot

work in progress

adding in more notes

chmod

bugfix : name mismatch

work in progress

bugfix : use ${VAR} for variable name

bugfix

wrong mount!

fix

bugfix attemp1

adding bugfix from

nodejs/corepack#550
RUN corepack enable && corepack install --global [email protected]
ENV COREPACK_ENABLE_DOWNLOAD_PROMPT=0

adding new script for debugging

adding new secrets

loading new char file

removing the hardcoded agent name

this should make it more flexible

untested: diagnosis steps

adding more debug statements to help diagnose the agent variables

removing error

cleaning up
@LeisureLinux
Copy link

I have the same issue, get hints from this thread, and by removing ~/.nvm, and
sudo npm install --yes --global corepack@latest
then
corepack -v && COREPACK_ENABLE_DOWNLOAD_PROMPT=0 corepack enable
the error disapear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants