daniel
/
distribution
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update garbage-collection.md (#3443)

master
Wang Jie 2017-06-03 01:00:20 +08:00 committed by Misty Stanley-Jones
parent a6fc3fa7fa
commit 78d250137b
1 changed files with 16 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/garbage-collection.md
View File

@ -37,7 +37,7 @@ Layers are therefore shared amongst manifests; each manifest maintains a referen
to the layer. As long as a layer is referenced by one manifest, it cannot be garbage to the layer. As long as a layer is referenced by one manifest, it cannot be garbage
collected. collected.
Manifests and layers can be 'deleted` with the registry API (refer to the API Manifests and layers can be `deleted` with the registry API (refer to the API
documentation [here](spec/api.md#deleting-a-layer) and documentation [here](spec/api.md#deleting-a-layer) and
[here](spec/api.md#deleting-an-image) for details). This API removes references [here](spec/api.md#deleting-an-image) for details). This API removes references
to the target and makes them eligible for garbage collection. It also makes them to the target and makes them eligible for garbage collection. It also makes them
@ -90,7 +90,7 @@ the blobs and if a blob's content address digest is not in the mark set, the
process will delete it. process will delete it.
> **NOTE** You should ensure that the registry is in read-only mode or not running at > **NOTE**: You should ensure that the registry is in read-only mode or not running at
> all. If you were to upload an image while garbage collection is running, there is the > all. If you were to upload an image while garbage collection is running, there is the
> risk that the image's layers will be mistakenly deleted, leading to a corrupted image. > risk that the image's layers will be mistakenly deleted, leading to a corrupted image.