docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add Stale image info under Viewing Repostories and markdown fix-ups 

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
Emilie Franchomme 2020-10-30 17:11:48 -04:00 committed by Sebastiaan van Stijn
parent 8822e9ae34
commit 161352b1b7
No known key found for this signature in database
GPG Key ID: 76698F39D527CE8C
4 changed files with 31 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
docker-hub/images/repo-overview.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 182 KiB

After

Width:  |  Height:  |  Size: 149 KiB

BIN
docker-hub/images/repo-tags-list.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 105 KiB

After

Width:  |  Height:  |  Size: 78 KiB

BIN
docker-hub/images/repos-create.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 120 KiB

After

Width:  |  Height:  |  Size: 50 KiB

44
docker-hub/repos.md
View File

@ -128,6 +128,23 @@ To view individual tags, click on the **Tags** tab.
![Manage Repo Tags](images/repo-tags-list.png)
An image is considered stale if there has been no push/pull activity for more
than 1 month, i.e.:
* It has not been pulled for more than 1 month
* And it has not been pushed for more than 1 month
A multi-architecture image is considered stale if all single-architecture images
part of its manifest are stale.
To delete a tag, select the corresponding checkbox and select **Delete** from the
**Action** drop-down list.
> **Note**
>
> Only a user with administrative access (owner or team member with Admin
> permission) over the repository can delete tags.
Select a tag's digest to view details.
![View Tag](images/repo-image-layers.png)
@ -185,20 +202,21 @@ workflows, and do not share Docker IDs with the members in the Team plan.
To create a new service account for your Team account:
1. Create a new Docker ID.
2. Create a [team](orgs.md#create-a-team) in your organization and grant it read-only access to your private repositories.
3. Add the new Docker ID to your [organization](orgs.md#working-with-organizations).
4. Add the new Docker ID to the [team](orgs.md#add-a-member-to-a-team) you created earlier.
5. Create a new [personal access token (PAT)](/access-tokens.md) from the user account and use it for CI.
1. Create a new Docker ID.
2. Create a [team](orgs.md#create-a-team) in your organization and grant it read-only access to your private repositories.
3. Add the new Docker ID to your [organization](orgs.md#working-with-organizations).
4. Add the new Docker ID to the [team](orgs.md#add-a-member-to-a-team) you created earlier.
5. Create a new [personal access token (PAT)](/access-tokens.md) from the user account and use it for CI.
To create a new service account for your Pro account:
1. Create a new Docker ID.
2. Click **Repositories** from the main menu.
3. Select a repository from the list and go to the **Collaborators** tab.
4. Add the new Docker ID as a collaborator.
5. Create a new [personal access token (PAT)](/access-tokens.md) from the user account and use it for CI.
1. Create a new Docker ID.
2. Click **Repositories** from the main menu.
3. Select a repository from the list and go to the **Collaborators** tab.
4. Add the new Docker ID as a collaborator.
5. Create a new [personal access token (PAT)](/access-tokens.md) from the user account and use it for CI.
> **Note**
>
> If you want a read-only PAT just for your open source repos, or to access official images and other public images, you do not have to grant any access permissions to the new Docker ID.
> **Note**
>
> If you want a read-only PAT just for your open source repos, or to access
> official images and other public images, you do not have to grant any access permissions to the new Docker ID.