adelorenzo/getting-started
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update docs/tutorial/image-building-best-practices/index.md

Browse Source 
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
This commit is contained in:
Stephen Turner 2020-10-23 10:27:11 +01:00 committed by GitHub
parent 2dd6853f0d
commit 5e2c627a0f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/tutorial/image-building-best-practices/index.md
View File

@ -1,6 +1,6 @@
## Security Scanning ## Security Scanning
When you have built an image, it is good practice to scan it for security vulnerabilities, using the `docker scan` command. When you have built an image, it is good practice to scan it for security vulnerabilities using the `docker scan` command.
Docker has partnered with [Snyk](http://snyk.io) to provide the vulnerability scanning service. Docker has partnered with [Snyk](http://snyk.io) to provide the vulnerability scanning service.
For example, to scan the `getting-started` image you created earlier in the tutorial, you can just type For example, to scan the `getting-started` image you created earlier in the tutorial, you can just type
@ -267,4 +267,3 @@ By understanding a little bit about how images are structured, we can build imag
Scanning images gives us confidence that the containers we are running and distributing are secure. Scanning images gives us confidence that the containers we are running and distributing are secure.
Multi-stage builds also help us reduce overall image size and increase final container security by separating Multi-stage builds also help us reduce overall image size and increase final container security by separating
build-time dependencies from runtime dependencies. build-time dependencies from runtime dependencies.