[Starlingx-discuss] Certification Problem
Good afternoon Community, we have install StarlingX Simplex All-In-One and established a remote connection to the cluster. We try to deploy the pod from following Kubernetes tutorial https://kubernetes.io/docs/tasks/run-application/run-stateless-application-d.... The Pod returns following error: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 7d9h default-scheduler Successfully assigned default/nginx-deployment-6b474476c4-shtph to controller-0 Normal Pulling 7d9h (x3 over 7d9h) kubelet Pulling image "nginx:1.14.2" Warning Failed 7d9h (x3 over 7d9h) kubelet Failed to pull image "nginx:1.14.2": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/nginx:1.14.2": failed to resolve reference "docker.io/library/nginx:1.14.2": failed to do request: Head https://registry-1.docker.io/v2/library/nginx/manifests/1.14.2: x509: certificate has expired or is not yet valid Warning Failed 7d9h (x3 over 7d9h) kubelet Error: ErrImagePull Normal BackOff 7d9h (x3 over 7d9h) kubelet Back-off pulling image "nginx:1.14.2" Warning Failed 7d9h (x3 over 7d9h) kubelet Error: ImagePullBackOff We have a certification error. Where do we need to ad what certificate? When we use minikube or microk8s we can pull the image. Kind reagrds, Thorsten
I am assuming registry-1.docker.io is a private registry that you setup. https://docs.starlingx.io/security/kubernetes/add-a-trusted-ca.html#starling... Greg. From: Thorsten Steuer <thorsten.steuer@acdp.at> Sent: Friday, April 30, 2021 5:32 AM To: starlingx-discuss@lists.starlingx.io Cc: Sebastian Kropatschek <sebastian.kropatschek@acdp.at> Subject: [Starlingx-discuss] Certification Problem [Please note: This e-mail is from an EXTERNAL e-mail address] Good afternoon Community, we have install StarlingX Simplex All-In-One and established a remote connection to the cluster. We try to deploy the pod from following Kubernetes tutorial https://kubernetes.io/docs/tasks/run-application/run-stateless-application-d.... The Pod returns following error: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 7d9h default-scheduler Successfully assigned default/nginx-deployment-6b474476c4-shtph to controller-0 Normal Pulling 7d9h (x3 over 7d9h) kubelet Pulling image "nginx:1.14.2" Warning Failed 7d9h (x3 over 7d9h) kubelet Failed to pull image "nginx:1.14.2": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/nginx:1.14.2": failed to resolve reference "docker.io/library/nginx:1.14.2": failed to do request: Head https://registry-1.docker.io/v2/library/nginx/manifests/1.14.2: x509: certificate has expired or is not yet valid Warning Failed 7d9h (x3 over 7d9h) kubelet Error: ErrImagePull Normal BackOff 7d9h (x3 over 7d9h) kubelet Back-off pulling image "nginx:1.14.2" Warning Failed 7d9h (x3 over 7d9h) kubelet Error: ImagePullBackOff We have a certification error. Where do we need to ad what certificate? When we use minikube or microk8s we can pull the image. Kind reagrds, Thorsten
Hi Greg, first of all, thank you very much for your great support for newbies. We have rolled out the following standard configuration according to the documentation. we were not aware that we had set up a local docker registry. system_mode: simplex dns_servers: - 8.8.8.8 - 8.8.4.4 external_oam_subnet: 10.10.10.0/24 external_oam_gateway_address: 10.10.10.1 external_oam_floating_address: 10.10.10.2 admin_username: admin admin_password: ########### ansible_become_pass: ########### # Add these lines to configure Docker to use a proxy server # docker_http_proxy: http://my.proxy.com:1080 # docker_https_proxy: https://my.proxy.com:1443 # docker_no_proxy: # - 1.2.3.4 How can we now retrospectively adjust the configuration so that we use now DockerHub automatically. Greetings, Sebastian Am 30.04.2021 um 13:11 schrieb Waines, Greg <Greg.Waines@windriver.com<mailto:Greg.Waines@windriver.com>>: I am assuming registry-1.docker.io<http://registry-1.docker.io/> is a private registry that you setup. https://docs.starlingx.io/security/kubernetes/add-a-trusted-ca.html#starling... Greg. From: Thorsten Steuer <thorsten.steuer@acdp.at<mailto:thorsten.steuer@acdp.at>> Sent: Friday, April 30, 2021 5:32 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Cc: Sebastian Kropatschek <sebastian.kropatschek@acdp.at<mailto:sebastian.kropatschek@acdp.at>> Subject: [Starlingx-discuss] Certification Problem [Please note: This e-mail is from an EXTERNAL e-mail address] Good afternoon Community, we have install StarlingX Simplex All-In-One and established a remote connection to the cluster. We try to deploy the pod from following Kubernetes tutorial https://kubernetes.io/docs/tasks/run-application/run-stateless-application-d.... The Pod returns following error: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 7d9h default-scheduler Successfully assigned default/nginx-deployment-6b474476c4-shtph to controller-0 Normal Pulling 7d9h (x3 over 7d9h) kubelet Pulling image "nginx:1.14.2" Warning Failed 7d9h (x3 over 7d9h) kubelet Failed to pull image "nginx:1.14.2": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/nginx:1.14.2<http://docker.io/library/nginx:1.14.2>": failed to resolve reference "docker.io/library/nginx:1.14.2<http://docker.io/library/nginx:1.14.2>": failed to do request: Head https://registry-1.docker.io/v2/library/nginx/manifests/1.14.2: x509: certificate has expired or is not yet valid Warning Failed 7d9h (x3 over 7d9h) kubelet Error: ErrImagePull Normal BackOff 7d9h (x3 over 7d9h) kubelet Back-off pulling image "nginx:1.14.2" Warning Failed 7d9h (x3 over 7d9h) kubelet Error: ImagePullBackOff We have a certification error. Where do we need to ad what certificate? When we use minikube or microk8s we can pull the image. Kind reagrds, Thorsten
You do not have to set up a local docker registry. I was incorrectly assuming you had from this error. I was incorrectly thinking that registry-1.docker.io was a private local docker registry ... which it is not. Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 7d9h default-scheduler Successfully assigned default/nginx-deployment-6b474476c4-shtph to controller-0 Normal Pulling 7d9h (x3 over 7d9h) kubelet Pulling image "nginx:1.14.2" Warning Failed 7d9h (x3 over 7d9h) kubelet Failed to pull image "nginx:1.14.2": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/nginx:1.14.2<http://docker.io/library/nginx:1.14.2>": failed to resolve reference "docker.io/library/nginx:1.14.2<http://docker.io/library/nginx:1.14.2>": failed to do request: Head https://registry-1.docker.io/v2/library/nginx/manifests/1.14.2: x509: certificate has expired or is not yet valid Warning Failed 7d9h (x3 over 7d9h) kubelet Error: ErrImagePull Normal BackOff 7d9h (x3 over 7d9h) kubelet Back-off pulling image "nginx:1.14.2" Warning Failed 7d9h (x3 over 7d9h) kubelet Error: ImagePullBackOff I don't know why you'd be getting that error from an image on docker hub. Can you do a "docker pull nginx:1.14.2" from the shell of starlingx's controller-0 ? Greg. From: Sebastian Kropatschek <sebastian.kropatschek@acdp.at> Sent: Friday, April 30, 2021 7:28 AM To: Waines, Greg <Greg.Waines@windriver.com> Cc: Thorsten Steuer <thorsten.steuer@acdp.at>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Certification Problem [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg, first of all, thank you very much for your great support for newbies. We have rolled out the following standard configuration according to the documentation. we were not aware that we had set up a local docker registry. system_mode: simplex dns_servers: - 8.8.8.8 - 8.8.4.4 external_oam_subnet: 10.10.10.0/24 external_oam_gateway_address: 10.10.10.1 external_oam_floating_address: 10.10.10.2 admin_username: admin admin_password: ########### ansible_become_pass: ########### # Add these lines to configure Docker to use a proxy server # docker_http_proxy: http://my.proxy.com:1080 # docker_https_proxy: https://my.proxy.com:1443 # docker_no_proxy: # - 1.2.3.4 How can we now retrospectively adjust the configuration so that we use now DockerHub automatically. Greetings, Sebastian Am 30.04.2021 um 13:11 schrieb Waines, Greg <Greg.Waines@windriver.com<mailto:Greg.Waines@windriver.com>>: I am assuming registry-1.docker.io<http://registry-1.docker.io/> is a private registry that you setup. https://docs.starlingx.io/security/kubernetes/add-a-trusted-ca.html#starling... Greg. From: Thorsten Steuer <thorsten.steuer@acdp.at<mailto:thorsten.steuer@acdp.at>> Sent: Friday, April 30, 2021 5:32 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Cc: Sebastian Kropatschek <sebastian.kropatschek@acdp.at<mailto:sebastian.kropatschek@acdp.at>> Subject: [Starlingx-discuss] Certification Problem [Please note: This e-mail is from an EXTERNAL e-mail address] Good afternoon Community, we have install StarlingX Simplex All-In-One and established a remote connection to the cluster. We try to deploy the pod from following Kubernetes tutorial https://kubernetes.io/docs/tasks/run-application/run-stateless-application-d.... The Pod returns following error: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 7d9h default-scheduler Successfully assigned default/nginx-deployment-6b474476c4-shtph to controller-0 Normal Pulling 7d9h (x3 over 7d9h) kubelet Pulling image "nginx:1.14.2" Warning Failed 7d9h (x3 over 7d9h) kubelet Failed to pull image "nginx:1.14.2": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/nginx:1.14.2<http://docker.io/library/nginx:1.14.2>": failed to resolve reference "docker.io/library/nginx:1.14.2<http://docker.io/library/nginx:1.14.2>": failed to do request: Head https://registry-1.docker.io/v2/library/nginx/manifests/1.14.2: x509: certificate has expired or is not yet valid Warning Failed 7d9h (x3 over 7d9h) kubelet Error: ErrImagePull Normal BackOff 7d9h (x3 over 7d9h) kubelet Back-off pulling image "nginx:1.14.2" Warning Failed 7d9h (x3 over 7d9h) kubelet Error: ImagePullBackOff We have a certification error. Where do we need to ad what certificate? When we use minikube or microk8s we can pull the image. Kind reagrds, Thorsten
participants (3)
-
Sebastian Kropatschek
-
Thorsten Steuer
-
Waines, Greg