hi, i'm getting an issue with corepack - it seems ...
# pulumi-deployments
b
hi, i'm getting an issue with corepack - it seems like the corepack isn't installed on the runner and is causing my deployments to fail - did something change?
r
What is corepack? But more generally, it sounds like something was working but now it's not? We had some recent changes with our docker containers. You might want to open an issue in https://github.com/pulumi/pulumi-docker-containers/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen
w
Corepack is a tool that ships with nodejs to manage the versions of package managers. We updated the base layer of our images to the latest debian version (from 11 to 12) and it looks like corepack went missing in the process. We’ll get this fixed, but in the mean time you can workaround this by specifying a different executor image for your deployments, see https://www.pulumi.com/docs/pulumi-cloud/deployments/reference/#customizing-the-deployment-environment You can either use the previous version of our multi language image
pulumi/pulumi:3.127.0
, or you could use the nodejs specific image
pulumi/pulumi-nodejs
, which is based on
node:18-bookworm-slim
and does include corepack.
b
Thank you for your help!
i'm getting this error, is there something else i need to set up?:
Copy code
Pulling container image "pulumi/pulumi:3.127.0" 
image pull failed; retrying
w
Oh, can you try with adding the registry to the image tag:
public.ecr.aws/pulumi/pulumi:3.127.0
r
That used to work though... did something change? I still see them on dockerhub.
b
hmm still getting the same error
Copy code
Pulling container image "public.ecr.aws/pulumi/pulumi:3.127.0" 
image pull failed; retrying
r
Is there more in the error after
retrying
?
b
nope, it just retries a couple times and says
giving up retry limit reached
r
Weird.. I just tried to repro but it works 😕
b
what am i supposed to put for image repository username and password? it looks like it automatically fills with my pulumi login email and password
w
The images public, so you should leave them empty in this case. These fields are for use with private Docker registries, and you would use login credentials for those registries in those fields.
So if it auto-filled the pulumi login and email, that’s probably the issue, since it will try to login to the registry with those creds.
b
everytime i save them empty and refresh the page the creds show up in the username and password fields😅
w
haha, indeed, I can repro that
Even turning off/on the custom executor checkbox won’t clear it
no hang on, turning off the custom executor checkbox, saving, reloading and then turning it back on works
b
hmm when i do that the image reference field clears but not the username or password haha i even tried opening a new window
w
Could it be your browser’s autofill that puts it back in this case?
b
yep youre right! i changed to an incognito browser and its able to pull the image now - thanks for your help!
w
Great! I’ll create a ticket for us to fix this annoying UI bug that prevents clearing the fields.
😀 1
b
hi Julien! i saw that the issue was closed, thank you for getting to it so quickly! i do see that i am still getting the corepack issue in my deployments, is there anything i need to do from my side?
r
Hey Rachel! The issue is closed because the PR was merged, but we'll need a new release of the docker image, followed by a release of pulumi cloud for this all to fix your deployment. Look out for that early next week.
b
got it, thank you!