mirror of https://github.com/docker/docs.git
edit: updated `Security scanning` section (#13546)
* edit: updated `Security scanning` section `docker scan` fails when user is not logged in to Docker Hub. First I had to use `docker login` to login to Docker Hub. Afterwards, `docker scan` worked. * Update 09_image_best.md Update format, fix a typo Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
This commit is contained in:
parent
45d436cb51
commit
24133a237c
|
@ -6,9 +6,14 @@ description: Tips for building the images for our application
|
|||
|
||||
## 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 a good practice to scan it for security vulnerabilities using the `docker scan` command.
|
||||
Docker has partnered with [Snyk](http://snyk.io){:target="_blank" rel="noopener" class="_"} to provide the vulnerability scanning service.
|
||||
|
||||
> **Note**
|
||||
>
|
||||
> You must be logged in to Docker Hub to scan your images. Run the command `docker login`, and then scan your images using
|
||||
> `docker scan <image-name>`.
|
||||
|
||||
For example, to scan the `getting-started` image you created earlier in the tutorial, you can just type
|
||||
|
||||
```console
|
||||
|
|
Loading…
Reference in New Issue