openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Code Issues Releases Activity

Added a known issue in the delete feature about container registry

Browse Source
This commit is contained in:
subhtk
2025-02-18 11:31:54 +05:30
committed by openshift-cherrypick-robot
parent 40a369ba76
commit 3977abbc9d
3 changed files with 64 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
disconnected/mirroring/about-installing-oc-mirror-v2.adoc
View File

@@ -89,6 +89,12 @@ After your cluster is configured to use the resources generated by oc-mirror plu
// workflows of delete feature
include::modules/oc-mirror-workflows-delete-v2.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
* xref:../../disconnected/mirroring/about-installing-oc-mirror-v2.adoc#oc-mirror-v2-procedure-garbage-collector_about-installing-oc-mirror-v2[Resolving storage cleanup issues in the distribution registry]
include::modules/oc-mirror-v2-procedure-garbage-collector.adoc[leveloffset=+2]
// procedure for delete feature
include::modules/oc-mirror-procedure-delete-v2.adoc[leveloffset=+2]
@@ -113,6 +119,7 @@ include::modules/oc-mirror-proxy-support.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
* xref:../../disconnected/updating/disconnected-update-osus.adoc#updating-disconnected-cluster-osus[Updating a cluster in a disconnected environment using the OpenShift Update Service]
* xref:../../disconnected/mirroring/about-installing-oc-mirror-v2.adoc#oc-mirror-v2-procedure-garbage-collector_about-installing-oc-mirror-v2[Resolving storage cleanup issues in the distribution registry]
//operator catalog filtering
include::modules/oc-mirror-operator-catalog-filtering.adoc[leveloffset=+1]

53
modules/oc-mirror-v2-procedure-garbage-collector.adoc Normal file
View File

@@ -0,0 +1,53 @@
// Module included in the following assemblies:
//
// * disconnected/mirroring/about-installing-oc-mirror-v2.adoc
:_mod-docs-content-type: PROCEDURE
[id="oc-mirror-v2-procedure-garbage-collector_{context}"]
= Resolving storage cleanup issues in the distribution registry
A known issue in the distribution registry prevents the garbage collector from freeing up storage as expected. This issue does not occur when you use {quay}.
.Procedure
* Choose the appropriate method to work around the known issue in the distribution registry:
** To restart the container registry, run the following command:
+
[source,terminal]
----
$ podman restart <registry_container>
----
** To disable caching in the registry configuration, perform the following steps:
... To disable the `blobdescriptor` cache, modify the `/etc/docker/registry/config.yml` file:
+
[source,yaml]
----
version: 0.1
log:
fields:
service: registry
storage:
cache:
blobdescriptor: ""
filesystem:
rootdirectory: /var/lib/registry
http:
addr: :5000
headers:
X-Content-Type-Options: [nosniff]
health:
storagedriver:
enabled: true
interval: 10s
threshold: 3
----
... To apply the changes, restart the container registry by running the following command:
+
[source,terminal]
----
$ podman restart <registry_container>
----

5
modules/oc-mirror-workflows-delete-v2.adoc
View File

@@ -52,7 +52,10 @@ Consider using the mirror-to-disk and disk-to-mirror workflows to reduce mirrori
oc-mirror plugin v2 deletes only the manifests of the images, which does not reduce the storage occupied in the registry.
To free up storage space from unnecessary images, such as those with deleted manifests, you must enable the garbage collector on your container registry. With the garbage collector enabled, the registry will delete the image blobs that no longer have references to any manifests, reducing the storage previously occupied by the deleted blobs. The process for enabling the garbage collector differs depending on your container registry.
To free up storage space from unnecessary images, such as those with deleted manifests, you must enable the garbage collector on your container registry. With the garbage collector enabled, the registry will delete the image blobs that no longer have references to any manifests, reducing the storage previously occupied by the deleted blobs. The process for enabling the garbage collector differs depending on your container registry.
For more information, see "Resolving storage cleanup issues in the distribution registry".
[IMPORTANT]
====