You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the Superchain image (1-buster-slim-node18 in my case) in GitLab CI and trying to install global NPM packages (e.g. npm i -g pnpm), the build fails with a permission denied error indicating that the superchain user has no permissions to write to /usr/lib/node_modules.
Expected Behavior
It should be possible to install global NPM packages out-of-the-box.
Current Behavior
Installing a global NPM package fails with a permission denied error.
Reproduction Steps
Run a GitLab CI job with the Superchain image and try to install a global package.
Possible Solution
Give the sufficient permissions to the superchain user (or add pnpm to the default tools 😉).
Additional Information/Context
Current workaround is to change the installation directory for global packages before installing them:
mkdir ~/npm-global
npm config set prefix '~/npm-global'
export PATH=~/npm-global/bin:$PATH
npm i -g pnpm
SDK version used
1-buster-slim-node18
Environment details (OS name and version, etc.)
1-buster-slim-node18 on GitLab CI
The text was updated successfully, but these errors were encountered:
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Describe the bug
When using the Superchain image (
1-buster-slim-node18
in my case) in GitLab CI and trying to install global NPM packages (e.g.npm i -g pnpm
), the build fails with a permission denied error indicating that thesuperchain
user has no permissions to write to/usr/lib/node_modules
.Expected Behavior
It should be possible to install global NPM packages out-of-the-box.
Current Behavior
Installing a global NPM package fails with a permission denied error.
Reproduction Steps
Run a GitLab CI job with the Superchain image and try to install a global package.
Possible Solution
Give the sufficient permissions to the
superchain
user (or add pnpm to the default tools 😉).Additional Information/Context
Current workaround is to change the installation directory for global packages before installing them:
SDK version used
1-buster-slim-node18
Environment details (OS name and version, etc.)
1-buster-slim-node18 on GitLab CI
The text was updated successfully, but these errors were encountered: