Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use docker scout command Fixes #394 #395

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+3 −3
Open

Use docker scout command Fixes #394 #395

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/tutorial/image-building-best-practices/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
## 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 scout` 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

```bash
docker scan getting-started
docker scout cves getting-started
```

The scan uses a constantly updated database of vulnerabilities, so the output you see will vary as new
Expand Down Expand Up @@ -34,7 +34,7 @@ vulnerabilities are discovered, but it might look something like this:
The output lists the type of vulnerability, a URL to learn more, and importantly which version of the relevant library
fixes the vulnerability.

There are several other options, which you can read about in the [docker scan documentation](https://docs.docker.com/engine/scan/).
There are several other options, which you can read about in the [docker scout documentation](https://docs.docker.com/scout/).

As well as scanning your newly built image on the command line, you can also [configure Docker Hub](https://docs.docker.com/docker-hub/vulnerability-scanning/)
to scan all newly pushed images automatically, and you can then see the results in both Docker Hub and Docker Desktop.
Expand Down