-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 build in devcontainer #12156
Comments
Can you describe the exact steps to reproduce? |
Sure, added repro steps to the description! |
Removing bug label, as this isn't a renovate bug, it's just a developper issue 🙃 BTW: I see a bug, the |
Reproduced, I think:
|
Strange, we never change permissions on |
|
maybe we need a new |
Vanilla buildpack works:
codespaces does not:
|
Shall we try #12165 ? |
Reopening, because I restated my codespaces and still get this:
|
This seems to be a workaround:
On a related note, I always see this: And clicking in EITHER button is a bad idea:
@JamieMagee can you be our hero here? :) |
Sure, I can take a look. We probably need to set a non- |
We are a non root user https://github.com/containerbase/node/blob/d503889b23bb740306ef700454321a7a871014e2/Dockerfile#L12 |
True, but there's a couple of related It does say it reads the last |
Output from
|
One difference I noticed: The user In the There is so much more going on in the default image that I'm wondering why not just switch (back) to it? |
so the problem seems to be the root group permissions on tmp 😕 We need this for openstack compabillity. |
@viceice can you elaborate? What do we set them to and does codespaces change it? Can we alternatively create our own tmp to use instead, Eg /usr/src/tmp ? (Note: lots of our docs may need to change..) |
I'm ok with using one of the default containers if we can't get our own working yet |
Let me try to fix it tomorrow. |
This should fix the issue |
While |
Shall we switch back to the standard image? Footnotes |
No, i think I'll try to find a fix |
@viceice Sorry to ping you here all the time but this really bugs me every time I want to do a smaller contribution. What do you think about moving to the standard image suggested by @JamieMagee until the issue in |
ok, will look at it now |
So my summary is, because our user is a member of root group we dont have access to drwxr-xrwt+ 2 root root 4096 Oct 14 08:49 tmp That why we switch to root user for now until we find a better solution. see #14652 |
🎉 This issue has been resolved in version 32.6.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Describe the bug
When opening this repository in a devcontainer config, e.g. in GitHub Codespaces
yarn install
fails due to missing permissions for/tmp
. To me it looks like/tmp
has incorrect permissions for the non-root user:Have you created a minimal reproduction repository?
No reproduction repository, but here are the steps:
yarn install
:The text was updated successfully, but these errors were encountered: