No Answers
- Newest
- Most votes
- Most comments
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked a year ago
- asked a month ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Seems like I got the same issue -> https://repost.aws/questions/QUAC3CfympT5SizfvCJBEFEQ#ANEgz8sZ9LTfS2oVcrlhV5ZQ . Switching from
node:16-alpine
tonode:16-slim
fixed the issue (which is what you did basically)