Skip to content

Commit 8cbc602

Browse files
author
Steven Smith
committed
Removes empty note
1 parent 04d2df8 commit 8cbc602

File tree

1 file changed

+0
-5
lines changed

1 file changed

+0
-5
lines changed

modules/installation-about-mirror-registry.adoc

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,4 @@ If choosing a container registry that is not the _mirror registry for Red Hat Op
2020

2121
When you populate your mirror registry with {product-title} images, you can follow two scenarios. If you have a host that can access both the internet and your mirror registry, but not your cluster nodes, you can directly mirror the content from that machine. This process is referred to as _connected mirroring_. If you have no such host, you must mirror the images to a file system and then bring that host or removable media into your restricted environment. This process is referred to as _disconnected mirroring_.
2222

23-
[NOTE]
24-
====
25-
26-
====
27-
2823
For mirrored registries, to view the source of pulled images, you must review the `Trying to access` log entry in the CRI-O logs. Other methods to view the image pull source, such as using the `crictl images` command on a node, show the non-mirrored image name, even though the image is pulled from the mirrored location.

0 commit comments

Comments
 (0)