OCNE: How To Pull Images Using CRIO Container From Insecure Private Mirror Container Registry?
(Doc ID 2958663.1)
Last updated on JUNE 30, 2023
Applies to:Oracle Cloud Native Environment (OCNE) - Version 1.5 and later
Information in this document applies to any platform.
This MOS Note provides detailed steps on how to pull images using CRIO Container from Insecure Private Mirror Container Registry.
CRIO is the default container runtime in Oracle Cloud Native Environment (OCNE). By default, CRIO will not connect to insecure private container registries. So if insecure private mirror registries are used (which do not have signed certs or using self-signed certs), you may notice issues of pod deployments failing on OCNE Kubernetes cluster due to CRIO not able to pull images from insecure private container registry. Steps in this MOS note will be useful to fix the issue of CRIO not pulling images from insecure private container registry. Steps in this MOS note enable insecure TLS handshake protocol on CRIO container runtime, which will enable CRIO to connect to insecure private mirror container registry.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document