Upstream/harbor
1
0
Fork 0
mirror of https://github.com/goharbor/harbor.git synced 2025-02-12 18:01:54 +01:00
Code Issues Projects Releases Wiki Activity

user guide

Browse Source
This commit is contained in:
Henry Zhang 2016-11-07 21:58:17 +08:00
parent 6d237bf69d
commit 876712a5ca
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/user_guide.md
View File

@ -153,6 +153,7 @@ $ docker push 10.117.169.182/demo/ubuntu:14.04
##Deleting repositories ##Deleting repositories
Repository deletion runs in two steps. Repository deletion runs in two steps.
First, delete a repository in Harbor's UI. This is soft deletion. You can delete the entire repository or just a tag of it. After the soft deletion, First, delete a repository in Harbor's UI. This is soft deletion. You can delete the entire repository or just a tag of it. After the soft deletion,
the repository is no longer managed in Harbor, however, the files of the repository still remains in Harbor's storage. the repository is no longer managed in Harbor, however, the files of the repository still remains in Harbor's storage.
@ -160,8 +161,7 @@ the repository is no longer managed in Harbor, however, the files of the reposit
**CAUTION: If both tag A and tag B refer to the same image, after deleting tag A, B will also get deleted.** **CAUTION: If both tag A and tag B refer to the same image, after deleting tag A, B will also get deleted.**
Next, delete the acutual files of the repository using the registry's garbage collection(GC). Next, delete the actual files of the repository using the registry's garbage collection(GC). Make sure that no one is pushing images or Harbor is not running at all before you perform a GC. If someone were pushing an image while GC is running, there is a risk that the image's layers will be mistakenly deleted which results in a corrupted image. So before running GC, a preferred approach is to stop Harbor first.
Make sure that no one is pushing images or Harbor is not running at all before you perform a GC. If someone were pushing an image while GC is running, there is a risk that the image's layers will be mistakenly deleted which results in a corrupted image. So before running GC, a preferred approach is to stop Harbor first.
Run the below commands on the host which Harbor is deployed on to preview what files/images will be affect: Run the below commands on the host which Harbor is deployed on to preview what files/images will be affect: