-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
Current Behavior
FROM ubuntu:22.04
ENV DEBIAN_FRONTEND noninteractive
ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true
RUN apt-get update -y
RUN apt-get upgrade -y
RUN apt-get install apt-utils -y
RUN apt-get install curl -y
RUN curl -fsSL https://deb.nodesource.com/setup_18.x | bash -
RUN apt-get install -y nodejs
RUN npm i npm -g && npm i lighthouse -g
When installing lighthouse in docker (perhaps also generally on linux), same files and folders have problematic uid.
Eg. lighthouse/node_modules/cssstyle has 829141562 and this cause us that docker wasn't able to pull the docker image on our remote server.
WARNING: Failed to pull image with policy "always": failed to register layer: Error processing tar file(exit status 1): Container ID 829141562 cannot be mapped to a host ID (manager.go:240:36s)Which led me to https://circleci.com/docs/high-uid-error/, but changing the uid via chown in docker didn't solve the issue.
After some digging I've found out that it was caused by npm@9, the issue was not happening in npm@8, perhaps because of changes in #5703
Expected Behavior
I've resolved this by installing lighthouse with npm@8 for now.
The changes in #5703 seems like a good aproach, and this is just an edge case issue, so maybe close it. Just wanted to raise awareness about this to anyone experiencing similar problems.
Steps To Reproduce
No response
Environment
- npm: 9.1.2
- Node.js: 18.12.1
- OS Name: Ubuntu 22.04
- System Model Name:
- npm config:
; node bin location = /usr/bin/node
; node version = v18.12.1
; npm local prefix = /
; npm version = 9.1.2
; cwd = /
; HOME = /root