-
Notifications
You must be signed in to change notification settings - Fork 2k
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
node:20.13 breaks building with workspaces from root #2081
Comments
Leaving the workdir undefined is the preferred behavior because it's an image that is used as a base for other images. The workdir can easily be set either in a dependent image or at runtime. |
indeed, working around it is quite easy. but I don't see documentation on actively setting the workdir when deriving an image. and it was working in the previous minor version so I see it as a regression on a LTS image, which might break a bunch of setup (it broke mine at least). |
It might be a change of behavior in npm that causes this to change within a major version. |
Environment
Expected Behavior
Building a workspace aware project without changing workdir.
Current Behavior
npm
fails stating that it can't find any workspace: "ERR! No workspaces found!"Possible Solution
setting WORKDIR to another dir than / before running
npm
fixes it.also using node:20.12 instead of node:20 (or node:20.13) fixes it.
Steps to Reproduce
The text was updated successfully, but these errors were encountered: