Unable to pull docker images into kubernets

[SnehaAdhikary]

What Happened?

Error from server (BadRequest): container "first" in pod "first-6994cd9fc6-6rljc" is waiting to start: image can't be pulled.

Attach the log file

minikube_service_d2aad944dd4c1c18315f191f988ae7e8459743e8_0.log

Operating System

Windows

Driver

Docker

[T-Lakshmi]

@SnehaAdhikary,
is docker daemon running in your machine?
Also please verify the provided image is existing or not.

[T-Lakshmi]

/triage needs-information

[SnehaAdhikary]

Yes docker is running and image is present in docker

[spowelljr]

Hi @SnehaAdhikary, the issue is you have the image built on your Docker Desktop instance, but minikube has its own Docker instance running inside of it. The minikube Docker instance can't see the images in Docker Desktop. There are multiple ways to resolve this, the easiest would be to copy the image into minikube Docker using the minikube image save command.

Ex.

minikube image load <image>

minikube image list

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[spowelljr]

Hi @SnehaAdhikary, we haven't heard back from you, do you still have this issue?
There isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate.

I will close this issue for now but feel free to reopen when you feel ready to provide more information.