From c8fee4f04be3c5737fd3fbbe13beffa090e2a1a8 Mon Sep 17 00:00:00 2001 From: Ville Valtonen Date: Wed, 1 Dec 2021 12:31:47 +0200 Subject: [PATCH] Update garbage-collection.md Based on the pull request distribution/distribution#2302 there is a parameter for cleaning up untagged manifests available. In the original pull request it is called "-m" / "--delete-manifests", but in the current version of registry and it's garbage-collector, it's called "--delete-untagged" (checked with "registry garbage-collect -h" inside the latest registry-image based container). Anyway, it was missing from the documentation so I thought it would be useful to add there. Related issue and PR: - https://github.com/distribution/distribution/issues/2301 - https://github.com/distribution/distribution/pull/2302 --- registry/garbage-collection.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/registry/garbage-collection.md b/registry/garbage-collection.md index 688238be83..8732c761eb 100644 --- a/registry/garbage-collection.md +++ b/registry/garbage-collection.md @@ -92,10 +92,10 @@ This type of garbage collection is known as stop-the-world garbage collection. Garbage collection can be run as follows -`bin/registry garbage-collect [--dry-run] /path/to/config.yml` +`bin/registry garbage-collect [--dry-run] [--delete-untagged] /path/to/config.yml` The garbage-collect command accepts a `--dry-run` parameter, which prints the progress -of the mark and sweep phases without removing any data. Running with a log level of `info` +of the mark and sweep phases without removing any data. If you need to clean up untagged manifests as well, you can run the command with `--delete-untagged` parameter. Running with a log level of `info` gives a clear indication of items eligible for deletion. The config.yml file should be in the following format: