Mlrun Jupyter- Image pull back off error

[harishgawade1999]

MLRun Version checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of MLRun CE.

Reproducible Example

kubectl create namespace mlrun
helm repo add mlrun-ce https://mlrun.github.io/ce
helm repo update

kubectl --namespace mlrun create secret docker-registry registry-credentials 
--docker-server="https://index.docker.io/v1/" 
--docker-username="xyz" 
--docker-password="xyz" 
--docker-email="xyz" 

helm --namespace mlrun 
install mlrun-ce 
--wait --timeout 960s 
--set global.registry.url="index.docker.io/xyz" 
--set global.registry.secretName=registry-credentials 
--set global.externalHostAddress=http://192.168.49.2 
mlrun-ce/mlrun-ce

Issue Description

I'm following mlrun Kubernetes installation kit. I'm following the way suggested by them, still getting "Mlrun Jupyter - 'Image pull back error '". so please guide me through this.

Expected Behavior

I'm using Kubectl, Minikube, helm, docker etc.

Installation OS

Windows

Installation Method

Kubernetes

Python Version

3.8

MLRun Version(CE)

0.5

Additional Information

No response

[Tankilevitch]

Hey @harishgawade1999 , can you please share the output of kubectl -n mlrun describe deployment mlrun-jupyter -o json and also please take a look at the suggestion in #2817 (comment) and let me know if that helps.

[harishgawade1999]

Hey @harishgawade1999 , can you please share the output of kubectl -n mlrun describe deployment mlrun-jupyter -o json and also please take a look at the suggestion in #2817 (comment) and let me know if that helps.

Name: mlrun-jupyter
Namespace: mlrun
CreationTimestamp: Tue, 03 Jan 2023 17:39:50 +0530
Labels: app.kubernetes.io/component=jupyter-notebook
app.kubernetes.io/instance=mlrun-ce
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=mlrun-ce
helm.sh/chart=mlrun-ce-0.5.0
Annotations: deployment.kubernetes.io/revision: 1
meta.helm.sh/release-name: mlrun-ce
meta.helm.sh/release-namespace: mlrun
Selector: app.kubernetes.io/component=jupyter-notebook,app.kubernetes.io/instance=mlrun-ce,app.kubernetes.io/name=mlrun-ce
Replicas: 1 desired | 1 updated | 1 total | 0 available | 1 unavailable
StrategyType: RollingUpdate
MinReadySeconds: 0
RollingUpdateStrategy: 25% max unavailable, 25% max surge
Pod Template:
Labels: app.kubernetes.io/component=jupyter-notebook
app.kubernetes.io/instance=mlrun-ce
app.kubernetes.io/name=mlrun-ce
Init Containers:
init-chown-data:
Image: busybox:1.35
Port:
Host Port:
Command:
chown
-R
1000:100
/home/jovyan/data
Environment:
Mounts:
/home/jovyan/data from notebooks (rw)
Containers:
jupyter-notebook:
Image: quay.io/mlrun/jupyter:1.1.1
Port: 8888/TCP
Host Port: 0/TCP
Command:
start-notebook.sh
Args:
--ip="0.0.0.0"
--port=8888
--NotebookApp.token=''
--NotebookApp.password=''
--NotebookApp.default_url="/lab"
Environment:
MLRUN_NAMESPACE: (v1:metadata.namespace)
JUPYTER_ENABLE_LAB: yes
MLRUN_DBPATH: http://mlrun-api:8080
MLRUN_UI_URL: http://localhost:30060
MLRUN_MPIJOB_CRD_VERSION: v1
MLRUN_PVC_MOUNT: mlrun-jupyter:/home/jovyan/data
CHOWN_HOME: yes
CHOWN_HOME_OPTS: -R
MLRUN_ARTIFACT_PATH: s3://mlrun/
S3_ENDPOINT_URL: http://minio.mlrun.svc.cluster.local:9000
AWS_SECRET_ACCESS_KEY: minio123
AWS_ACCESS_KEY_ID: minio
MLRUN_CE: true
Mounts:
/home/jovyan/data from notebooks (rw)
Volumes:
notebooks:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: mlrun-jupyter
ReadOnly: false
Conditions:
Type Status Reason

---

Available False MinimumReplicasUnavailable
Progressing False ProgressDeadlineExceeded
OldReplicaSets:
NewReplicaSet: mlrun-jupyter-74f566dfdc (1/1 replicas created)
Events:
Type Reason Age From Message

---

Normal ScalingReplicaSet 12m deployment-controller Scaled up replica set mlrun-jupyter-74f566dfdc to 1

[harishgawade1999]

Hey @harishgawade1999 , can you please share the output of kubectl -n mlrun describe deployment mlrun-Jupyter -o json and also please take a look at the suggestion in #2817 (comment) and let me know if that helps.

I also did all the suggestions described in #2817 PR. but still getting same error. I also pulled Jupyter image separately & its being pulled separately. so I don't know what is the cause of this error. so, please guide me through this.

[quaark]

Hey @harishgawade1999 ,
Sorry to hear it didn't work.
When you tried to docker pull the image did you do it within the minikube machine?
Make sure you first run:

minikube ssh

And then:

docker pull quay.io/mlrun/jupyter:1.1.1

[harishgawade1999]

minikube ssh

Thanks for your reply. if i separately pulled this docker image, then i m able to pull it. but im unable to pull it through helm chart. so can u please guide me through this. i mean what changes i have to make and where?

[harishgawade1999]

Thank you so much for your help. my error has been solved. so because of that, closing this issue.