amitsadaphule edited a comment on issue #1869:
URL: https://github.com/apache/camel-k/issues/1869#issuecomment-765450861
Same issue even after deleting ik, it and re-executing `./kamel run
examples/Sample.java`.
```
# kubectl get all -n default
NAME READY STATUS RESTARTS
AGE
pod/camel-k-operator-57bbcbd6dc-j5kcv 1/1 Running 0
4h28m
pod/sample-95d958b69-z556d 0/1 ImagePullBackOff 0
55s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 10d
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/camel-k-operator 1/1 1 1 4h28m
deployment.apps/sample 0/1 1 0 56s
NAME DESIRED CURRENT READY AGE
replicaset.apps/camel-k-operator-57bbcbd6dc 1 1 1
4h28m
replicaset.apps/sample-95d958b69 1 1 0 56s
```
```
# kubectl get ik,it -A
NAMESPACE NAME PHASE
TYPE IMAGE
default integrationkit.camel.apache.org/kit-c05e6g5f57dq9p35q41g Ready
platform
10.103.184.236/default/camel-k-kit-c05e6g5f57dq9p35q41g@sha256:bb486d97a46e7d45e55497c99d01d869bfb1c71023220dda2c7d1343ed6bc200
NAMESPACE NAME PHASE KIT
REPLICAS
default integration.camel.apache.org/sample Running
kit-c05e6g5f57dq9p35q41g 1
```
```
# kubectl describe pod sample-95d958b69-z556d -n default
...
...
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 2m22s default-scheduler Successfully
assigned default/sample-95d958b69-z556d to p006vm87
Normal Pulling 55s (x4 over 2m18s) kubelet Pulling image
"10.103.184.236/default/camel-k-kit-c05e6g5f57dq9p35q41g@sha256:bb486d97a46e7d45e55497c99d01d869bfb1c71023220dda2c7d1343ed6bc200"
Warning Failed 55s (x4 over 2m18s) kubelet Failed to pull
image
"10.103.184.236/default/camel-k-kit-c05e6g5f57dq9p35q41g@sha256:bb486d97a46e7d45e55497c99d01d869bfb1c71023220dda2c7d1343ed6bc200":
rpc error: code = Unknown desc = Error response from daemon: Get
https://10.103.184.236/v2/: dial tcp 10.103.184.236:443: connect: connection
refused
Warning Failed 55s (x4 over 2m18s) kubelet Error:
ErrImagePull
Normal BackOff 44s (x6 over 2m17s) kubelet Back-off
pulling image
"10.103.184.236/default/camel-k-kit-c05e6g5f57dq9p35q41g@sha256:bb486d97a46e7d45e55497c99d01d869bfb1c71023220dda2c7d1343ed6bc200"
Warning Failed 29s (x7 over 2m17s) kubelet Error:
ImagePullBackOff
```
Maybe something is wrong with the registry setup itself? Is there a
different way to setup the local registry for minikube instead of `minikube
addons enable registry` that is known to be working for camel-k?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]