🔒 [security fix] Run container as non-root user#92
Conversation
- Switch to 'node' user in Dockerfile - Set proper ownership for /app directory and files - Update npm cache mount for non-root access Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
🎯 What: Modified the Dockerfile to run the application as the non-root
nodeuser instead ofroot.rootincreases the risk if the application is compromised. An attacker could potentially gain root access to the container, making it easier to escape the container or access sensitive host resources.🛡️ Solution:
nodeuser provided by the base image./appdirectory and its contents are owned by thenodeuser.nodeuser.PR created automatically by Jules for task 17915203525899158463 started by @max-ostapenko