From 5e2c627a0f929891d55592432886b0278011afd2 Mon Sep 17 00:00:00 2001 From: Stephen Turner Date: Fri, 23 Oct 2020 10:27:11 +0100 Subject: [PATCH] Update docs/tutorial/image-building-best-practices/index.md Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com> --- docs/tutorial/image-building-best-practices/index.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/tutorial/image-building-best-practices/index.md b/docs/tutorial/image-building-best-practices/index.md index e744a05..19f13ba 100644 --- a/docs/tutorial/image-building-best-practices/index.md +++ b/docs/tutorial/image-building-best-practices/index.md @@ -1,6 +1,6 @@ ## 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. 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. Multi-stage builds also help us reduce overall image size and increase final container security by separating build-time dependencies from runtime dependencies. -