Merge pull request #9384 from DawnWood-Docker/private-to-public

Private to public
This commit is contained in:
Dawn W 2019-09-05 17:33:48 -07:00 committed by GitHub
commit 71c3891877
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
14 changed files with 38 additions and 74 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 477 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 377 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 273 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 182 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 243 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 282 KiB

View File

@ -62,19 +62,28 @@ these efforts.
## Official Image Vulnerability Scanning
Each of the images in the Official Images is scanned for vulnerabilities. The results of
these security scans provide valuable information about which images contain
security vulnerabilities, and allow you to choose images that align with your
security standards.
Each of the images in the Official Images is scanned for vulnerabilities. The
results of these security scans provide valuable information about which images
contain security vulnerabilities, and allow you to choose images that align with
your security standards.
To view the Docker Security Scanning results:
1. Make sure you're logged in to Docker Hub.
You can view Official Images even while logged out, however the scan results are only available once you log in.
2. Navigate to the repository of the Official Image whose security scan you want to view.
3. Click the `Tags` tab to see a list of tags and their security scan summaries.
1. Make sure you're logged in to Docker Hub. You can view Official Images even
while logged out, however the scan results are only available once you log
in.
2. Navigate to the repository of the Official Image whose security scan you want
to view.
3. Click the `Tags` tab to see a list of tags. and their security scan summaries.
![Official Image Tags](images/official_images-tags-home.png)
4. Click on a tag to see the image's security scan summary.
![Official Image Tags](images/official_images-tags-2019.png)
![Official Image Tags](images/official_images-tags.png)
You can click into a tag's detail page to see more information about which
layers in the image and which components within the layer are vulnerable.

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 24 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 8.3 KiB

After

Width:  |  Height:  |  Size: 33 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 442 KiB

After

Width:  |  Height:  |  Size: 474 KiB

View File

@ -208,54 +208,19 @@ To interpret the results of a scanned image:
1. Log on to [Docker Hub](https://hub.docker.com){: target="_blank" class="_"}.
2. Navigate to the repository details page (for example,
[Nginx](https://hub.docker.com/images/nginx){: target="_blank" class="_"}).
3. Click **View Available Tags** under the pull command in the upper right of
the UI.
Displalyed is a list of each tag scan with its age. A solid green bar
indicates a clean scan without known vulnerabilities. Yellow, orange, and
red indicate minor, major, and critical vulnerabilities respectively.
[busybox](https://hub.docker.com/_/busybox){: target="_blank" class="_"}).
3. Click **Tags**.
![Scanned tags](images/scan-tags.png)
In this section, you can now view the different architectures separately to easily identify the right image for the architecture you need, complete with image size and operating system information.
![system info](images/Docker-Hub-tags-system-info.png)
> Vulnerability scores
>
> Vulnerability scores are defined by the entity that issues the
> vulnerability, such as [NVD](https://nvd.nist.gov/){: target="_blank" class="_"},
> and are based on a
> [Qualitative Severity Rating Scale](https://www.first.org/cvss/specification-document#5-Qualitative-Severity-Rating-Scale){: target="_blank" class="_"}
> defined as part of the
> [Common Vulnerability Scoring System (CVSS) specification](https://www.first.org/cvss/specification-document){: target="_blank" class="_"}.
4. Click on the digest for a particular architecture, you will now also be able to see the actual source of the image the layer-by-layer details that make up the image. ![system info](images/Docker-Hub-tags-vulnerabilities.png)
4. Click a scan summary to see a list of results for each layer of the image.
5. Click on the first row, youll see that the image contains multiple components and that multiple components have known vulnerabilities ranging from minor to critical. To explore further, click on the caret to expand and view all of the found vulnerabilities:
Each layer may have one or more scannable components represented by colored
squares in a grid.
![Scanned results](images/scan-view.png)
> Base layers
>
> Base layers contain components that are included in the parent image,
> but that you did not build and may not be able to edit. If a base layer
> has a vulnerability, switch to a version of the parent image that does not
> have any vulnerabilities, or to a similar but more secure image.
5. Hover over a square in the grid, then click to see the vulnerability report
for that specific component.
Only components that add software are scanned. If a layer has
no scannable components, it shows a `No components in this layer` message.
![Scanned component preview](images/scan-single.png)
6. Click the arrow icon (twice) to expand the list and show all vulnerable
components and their CVE report codes.
![Scanned components](images/scan-full-details.png)
7. Click one of the CVE codes to view the original vulnerability report.
![Scanned components](images/Docker-hub-tags-vulnerability-details.png)
Each vulnerability is linked directly to the CVE so that you can learn more about the CVE and its implications.
#### Classification of issues
@ -333,21 +298,6 @@ Docker Hub promotes Docker Certified Containers and Plugins running on Docker
Certified Infrastructure trusted and high quality content. The Docker Certified badge
can also be listed alongside external references to your product.
#### How is the Docker Certified Container image listed on Docker Hub?
These images are differentiated from other images through a
certification badge. A user can search specifically for CIs by limiting their
search parameters to show only certified content.
![certified content example](images/FAQ-certified-content.png)
#### Is certification optional or required?
Certification is recommended for all commercial and supported container images.
Free, community, and other commercial (non-certified) content may also be listed
on Docker Hub.
![certified content example](images/FAQ-types-of-certified-content.png)
#### How is support handled?

View File

@ -101,18 +101,23 @@ see the [organizations documentation](/docker-hub/orgs.md).
## Viewing repository tags
Docker Hub's repository "Tags" view shows you the available tags and the size
of the associated image.
Docker Hub's individual repositories view shows you the available tags and the
size of the associated image. Go to the "Repositories" view and click on a
repository to see its tags.
![View Repo Tags](images/repos-tags-view.png)
![Repository View](images/repo-view-2019.png)
![View Repo Tags](images/repos-tags-view-2019.png)
Image sizes are the cumulative space taken up by the image and all its parent
images. This is also the disk space used by the contents of the .tar file created
when you `docker save` an image.
images. This is also the disk space used by the contents of the .tar file
created when you `docker save` an image.
To edit tags, click on Manage Repository or find your repository under *Repositories*:
To view tags, click on "Tags" tab and then select a tag to view.
![Manage Repo Tags](images/repos-tags-manage.png)
![Manage Repo Tags](images/repos-tags-manage-2019.png)
![View Tag](images/repo-single-tag-view-2019.png)
## Searching for Repositories