This message was deleted.

PS C:\Users\boneis\rancher\nginx> kubectl run hello-world --image=nginx-helloworld:latest --image-pull-policy=Never --port=80 pod/hello-world created PS C:\Users\boneis\rancher\nginx> kubectl port-forward pods/hello-world 8080:80 error: unable to forward port because pod is not running. Current status=Pending PS C:\Users\boneis\rancher\nginx> kubectl port-forward pods/hello-world 8080:80 error: unable to forward port because pod is not running. Current status=Pending PS C:\Users\boneis\rancher\nginx> kubectl port-forward pods/hello-world 8080:80 error: unable to forward port because pod is not running. Current status=Pending PS C:\Users\boneis\rancher\nginx> kubectl get pods NAME READY STATUS RESTARTS AGE hello-world 0/1 ErrImageNeverPull 0 24s ErrImageNeverPull ??

If you set

--image-pull-policy=Never

then how is the image going to be pulled to your kubernetes (Rancher Desktop) cluster?

may be yes. ^^;

Okay. Were you following the

nerdctl

or the

docker

instructions?

docker

Okay. Just doing the

docker build --tag...

should have made the image available to your cluster. Let me just replicate the process...

docker build --tag nginx-helloworld:latest .

Can you do

kubectl config get-contexts

just to check your kubectl config is pointing to your local Rancher Desktop context.

$ kubectl config get-contexts 
CURRENT   NAME                             CLUSTER            AUTHINFO           NAMESPACE
*         rancher-desktop                  rancher-desktop    rancher-desktop

rancher-desktop

The instructions work exactly as expected for me...

$ kubectl get pods
NAME          READY   STATUS    RESTARTS   AGE
hello-world   1/1     Running   0          52s

same..

I'm out of ideas 😞

Thanks a lot

How curious. Oh well - at least it's working now 🙂

All of this is thanks to you. thank you so much.