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.

Sign up for GitHub

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

Jump to bottom

Npm version 9.5.0 is incompatible with Docker when userns-remap feature is enabled #1416

Closed
tbouliere-datasolution opened this issue Apr 18, 2023 · 1 comment · Fixed by #1423
Closed

Npm version 9.5.0 is incompatible with Docker when userns-remap feature is enabled #1416

tbouliere-datasolution opened this issue Apr 18, 2023 · 1 comment · Fixed by #1423
Assignees
@shauke
Labels
bug Something isn't working
Milestone
4.1

Comments

@tbouliere-datasolution
Copy link
Contributor

tbouliere-datasolution commented Apr 18, 2023 •
edited by azure-boards bot

Since version 4.0.0, pwa uses npm 9.5.0.
Is this incompatible with systems that use the docker userns-remap feature (npm/cli#5900)?

The Azure App Service uses this type of functionality.
This leads to strange runtime errors like this one during the docker extraction phase

ERROR - failed to register layer: Error processing tar file(exit status 1): Container ID 1389985163 cannot be mapped to a host IDErr: 0, Message: failed to register layer: Error processing tar file(exit status 1): Container ID 1389985163 cannot be mapped to a host ID

We have fixed this on our projet by updating the node image node:18.16.0-alpine.

AB#85447
@tbouliere-datasolution tbouliere-datasolution added the bug Something isn't working label Apr 18, 2023
@shauke shauke added this to the 4.1 milestone Apr 24, 2023
@shauke shauke self-assigned this Apr 24, 2023
shauke added a commit that referenced this issue Apr 24, 2023
@shauke
deps: update to use Node.js 18.16.0 with npm 9.5.1 to solve issue #1416
dcf1e6e
@shauke shauke mentioned this issue Apr 24, 2023
Merged
shauke added a commit that referenced this issue Apr 25, 2023
@shauke
deps: update to use Node.js 18.16.0 with npm 9.5.1 to solve issue #1416
3f4f3ac
shauke added a commit that referenced this issue Apr 25, 2023
@shauke
deps: update to use Node.js 18.16.0 with npm 9.5.1 to solve issue #1416…
35adb46 
… (#1423)
shauke added a commit that referenced this issue May 12, 2023
@shauke
deps: update to use Node.js 18.16.0 with npm 9.5.1 to solve issue #1416…
c4c989c 
… (#1423)

(cherry picked from commit 35adb46)
shauke added a commit that referenced this issue May 19, 2023
@shauke
deps: update to use Node.js 18.16.0 with npm 9.5.1 to solve issue #1416…
f946869 
… (#1423)

(cherry picked from commit 35adb46)
@shauke shauke pinned this issue May 22, 2023
@shauke
Copy link
Member

shauke commented May 22, 2023

Please cherry pick this commit to solve the issue in 4.0.0 based projects.
35adb46

The fix will be part of the 4.1.0 PWA release.

shauke added a commit that referenced this issue May 23, 2023
@shauke
deps: update to use Node.js 18.16.0 with npm 9.5.1 to solve issue #1416…
b7cbd62 
… (#1423)

(cherry picked from commit 35adb46)
@shauke shauke unpinned this issue Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shauke shauke

Labels
bug Something isn't working
Projects
None yet
Milestone
4.1
Development

Successfully merging a pull request may close this issue.

deps: node.js 18.16.0 + npm 9.5.1 intershop/intershop-pwa
2 participants
@shauke @tbouliere-datasolution