Open
Description
Nodejs container image version 16.14.2-slim deployed in AWS Fargate failed to start suddenly with loading the webpack and suggesting to add "chmod 1000:0 /root/.npm/". Worked after adding the RUN chmod 1000:0 /root/.npm/ in Dockerfile. However we are not sure what would have made this behaviour to suddenly failed when the same Dockerfile without "chmod 1000:0 /root/.npm/" Worked before. Understand that there is no support for 16.14.2. But, Just wanted to understand the root cause of this so it doesnt occur again.
Environment- Production
- Platform: AWS Fargate
- Docker Version: 16.14.2
- Node.js Version: node-v10.18.1 , npm-6.13.4
- Image Tag: 16.14.2-slim
Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce
Additional Information
Metadata
Metadata
Assignees
Labels
No labels