Add note about command "system registry-garbage-collect" (r6,r8,dsR8,dsR6)

Closes-bug: 2033096

Change-Id: Ibc093b7eebcc5c5f75b4277bdaf2f91b0c50bd78
Signed-off-by: Elisamara Aoki Goncalves <elisamaraaoki.goncalves@windriver.com>
This commit is contained in:
Elisamara Aoki Goncalves 2023-08-25 18:23:30 +00:00
parent 0df05f304c
commit ca817481bd
3 changed files with 18 additions and 0 deletions

View File

@ -74,6 +74,12 @@ associated space from the file system. To do so, you must also run the
**image:tags** from the file system and frees the file system spaces
allocated to deleted/unreferenced images.
.. note::
The :command:`registry-garbage-collect` command executes background
tasks that may affect access to the docker registry. It is recommended
to wait a few minutes before executing other registry related commands.
.. code-block:: none
~(keystone_admin)]$ system registry-garbage-collect

View File

@ -94,6 +94,12 @@ the local Docker registry's file system (`docker-distribution`) becomes full.
read-only mode. If this occurs, run garbage-collect again to take the
registry out of read-only mode.
.. note::
The :command:`registry-garbage-collect` command executes background
tasks that may affect access to the docker registry. It is recommended
to wait a few minutes before executing other registry related commands.
``registry-image-delete``
Remove the specified Docker image from the local registry.

View File

@ -57,6 +57,12 @@ to controller-1 and perform the same steps.
# SSH to controller-1 (or the standby controller)
crictl rmi registry.local:9001/quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0
.. note::
The :command:`registry-garbage-collect` command executes background
tasks that may affect access to the docker registry. It is recommended
to wait a few minutes before executing other registry related commands.
#. To reapply the application run the following command:
.. code-block:: none