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

moved these files to a new branch 

added diagrams to illustrate process of GC

added arrow back after talking to Jon

Signed-off-by: Carol Fager-Higgins <carol.fager-higgins@docker.com>
This commit is contained in:
Carol Fager-Higgins 2016-01-06 16:43:52 -08:00
parent f01a776f4d
commit 15a0366fee
4 changed files with 11 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
assets/gc1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 25 KiB

BIN
assets/gc2.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 54 KiB

BIN
assets/gc3.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 29 KiB

17
soft-garbage.md
View File

@ -23,11 +23,16 @@ layers. Tags, which are labels applied to images, point to manifests. You can
reference an image by tag or directly by the hash of the manifest. If you reference an image by tag or directly by the hash of the manifest. If you
purposefully delete one of those manifests and the image layers referenced by purposefully delete one of those manifests and the image layers referenced by
that manifest become orphaned, then they can be removed during the garbage that manifest become orphaned, then they can be removed during the garbage
collection job. This occurs if they are not referenced by other manifests. collection job. In the following diagram, _both_ manifests point to the first layer, #2543d8.
Since many developers may use a base image for future images, it is possible that there will be image layers that will never be deleted. There might ![Garbage collection illustration</soft-garbage/>](assets/gc1.png)
be other manifests that point to layers of the base image which could still be
used by others. Since many developers may use a base image for future images, it is possible
that there will be image layers that will never be deleted. There might be other
manifests that point to layers of the base image which could still be used by
others as seen in the second diagram.
![Garbage collection illustration</soft-garbage/>](assets/gc3.png)
## Prerequisites ## Prerequisites
You need an image to remove. You need an image to remove.
@ -98,9 +103,9 @@ deleted. Docker recommends performing garbage collection weekly during off time.
While garbage collection is occurring, anyone who tries to push an image will While garbage collection is occurring, anyone who tries to push an image will
get an error message. get an error message.
## See your garbage collection results ## View your garbage collection results
View your results by running the following example in a Trusted Registry CLI: See your results by running the following example in a Trusted Registry CLI:
``` ```
curl -u <username>:<password> https://<DTR curl -u <username>:<password> https://<DTR