From 9d2a4d749a8f5ae940ef6c8be6a213115bed687f Mon Sep 17 00:00:00 2001 From: Celestino Rey Date: Sat, 28 Jan 2023 15:46:03 +0100 Subject: [PATCH] =?UTF-8?q?A=C3=B1ado=20nota=20a=20las=20instrucciones?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...PrivateDockerRegistryasaPodinKubernetes.md | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/MiRegistry/DeployYourPrivateDockerRegistryasaPodinKubernetes.md b/MiRegistry/DeployYourPrivateDockerRegistryasaPodinKubernetes.md index 30d6cd0e..db0de0ae 100755 --- a/MiRegistry/DeployYourPrivateDockerRegistryasaPodinKubernetes.md +++ b/MiRegistry/DeployYourPrivateDockerRegistryasaPodinKubernetes.md @@ -187,6 +187,30 @@ tls.crt tls.crt 100% 1822 1.6MB/s 00:00 tls.crt 100% 1822 2.1MB/s 00:00 root@master1:/# + + + +NOTA: en containerd el directorio es + + +/etc/containers/certs.d/$REGISTRY_NAME/ + + +Por lo que lo mejor es: + +1) crear el directorio /etc/containers +2) establecer un enlace simbólico a /etc/dockers/certs.d con + + +sudo mkdir /etc/containers +cd /etc/containers +sudo ln -s /etc/docker/certs.d certs.d + +y luego + +sudo systemctl restart containerd + + The above step forces Docker to verify our self-signed certificate even though it is not signed by a known authority. Step 6: Testing our Private Docker Registry Now, let us try to login to the registry from the master node, using the same credentials we created earlier: