mirror of
https://github.com/goldbergyoni/nodebestpractices.git
synced 2025-10-30 17:17:03 +08:00
@ -1262,7 +1262,7 @@ In addition, referring to an image tag means that the base image is subject to c
|
|||||||
|
|
||||||
**TL;DR:** Linting your Dockerfile is an important step to identify issues in your Dockerfile which differ from best practices. By checking for potential flaws using a specialised Docker linter, performance and security improvements can be easily identified, saving countless hours of wasted time or security issues in production code.
|
**TL;DR:** Linting your Dockerfile is an important step to identify issues in your Dockerfile which differ from best practices. By checking for potential flaws using a specialised Docker linter, performance and security improvements can be easily identified, saving countless hours of wasted time or security issues in production code.
|
||||||
|
|
||||||
**Otherwise:** Mistakenely the Dockerfile creator left Root as the production user, and also used an image from unknown source repository. This could be avoided with with just a simple linter.
|
**Otherwise:** Mistakenly the Dockerfile creator left Root as the production user, and also used an image from unknown source repository. This could be avoided with with just a simple linter.
|
||||||
|
|
||||||
🔗 [**Read More: Lint your Dockerfile**](/sections/docker/lint-dockerfile.md)
|
🔗 [**Read More: Lint your Dockerfile**](/sections/docker/lint-dockerfile.md)
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user