Skip to content

Conversation

@ajeetraina
Copy link
Contributor

  • Use node:24-alpine base image
  • Run as non-root user (node) for security
  • Create /etc/todos directory with proper permissions

Description

Related issues or tickets

Reviews

  • Technical review
  • Editorial review
  • Product review

- Use node:24-alpine base image
- Run as non-root user (node) for security
- Create /etc/todos directory with proper permissions
@netlify
Copy link

netlify bot commented Jan 21, 2026

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 8aa5e68
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6971d0cf256286000877512a
😎 Deploy Preview https://deploy-preview-24003--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@MikeMcC399
Copy link

The Dockerfile is now more complex that the original one. The extra steps:

  • adding node user
  • removing the npm package manager

either need to be explained, or they should be omitted and left for a later stage where optimizations, such as security / reducing image size, etc. can be described.

@ajeetraina
Copy link
Contributor Author

ajeetraina commented Jan 22, 2026

@MikeMcC399 If you notice Parts 5 (Bind Mounts), 7 (Docker Compose), and 8 (Image-building best practices) all still use yarn install && yarn run dev commands throughout. We might need to work on revamping the entire workshop to migrate consistently from Yarn to npm across all parts. This will ensure a cohesive learning experience while addressing the Yarn v1 deprecation properly. Will update this PR once the comprehensive changes are ready.

Regarding the USER entry in the Dockerfile - it's required. Otherwise, users will encounter permission issues. I can add 1-2 lines explaining what it is and why it is required.

Updated the explanation of the Dockerfile to provide a detailed breakdown of its components and functionality.
@ajeetraina
Copy link
Contributor Author

@craig-osterhout @MikeMcC399 I will be raising a separate PR that replaces all occurances of Yarn with NPM in order to maintain consistency.

@MikeMcC399
Copy link

@ajeetraina

I will be raising a separate PR that replaces all occurances of Yarn with NPM in order to maintain consistency.

Why not add the changes into this PR? They belong together.

Also, if you are writing "npm", you should use lower case. See https://github.com/npm/cli#faq-on-branding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/get-started Relates to get started and onboarding docs status/review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants