Rafael Rodrigues Santana10/31/2022, 5:21 PM
. Sometimes, when trying to open Jupyter Lab, it get stuck trying to open it. Usually, this occurs when there is something wrong with the environment configuration. However, today we started to experience this in all projects that we have. By inspect one of the containers that was trying to launch the Jupyter Lab, it seems that the problem is occurring in the docker pull step as shown by the log below:
Any thoughts on this issue?
Error response from daemon: Get "<https://10.100.0.2/v2/>": dial tcp 10.100.0.2:443: connect: connection refused Docker pull failed, pulling with buildah. Trying to pull 10.100.0.2/orchest-env-bf496ede-cc70-4b92-b178-e4ab3929d5e9-d81de297-27a0-4864-8e85-584709a3ab7a:3... initializing source <docker://10.100.0.2/orchest-env-bf496ede-cc70-4b92-b178-e4ab3929d5e9-d81de297-27a0-4864-8e85-584709a3ab7a:3>: pinging container registry 10.100.0.2: Get "<http://10.100.0.2/v2/>": dial tcp 10.100.0.2:80: i/o timeout
(pull_image.sh). @Rafael Rodrigues Santana Did you change any configuration of the container runtime on your cluster (seems like you are using Docker)?
Jacopo11/01/2022, 8:39 AM
is the IP in use by the registry service created by Orchest? (
) • what AMI is being used for the EKS node? Anything custom?
kubectl get services -n orchest | grep docker-registry
Navid H11/01/2022, 9:13 AM
kubectl get deployment docker-registry -n orchest
Rafael Rodrigues Santana11/01/2022, 6:03 PM