X Exiting due to GUEST_IMAGE_LOAD

[NileshAhirrao]

What Happened?

Getting below error while running command on Windows10: minikube image load kubernetes-test-app:latest

X Exiting due to GUEST_IMAGE_LOAD: Failed to load image: save to dir: caching images: caching image "C:\Users\User\.minikube\cache\images\amd64\kubernetes-test-app_latest": write: unable to calculate manifest: blob sha256:4e4b4c647fc89b6328ca1647f8c5a54abe4a89873307bd76501f6dd20df57a4a not found

Attach the log file

Log file created at: 2025/04/05 22:41:15
Running on machine: DESKTOP-3RI4QR8
Binary: Built with gc go1.21.3 for windows/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I0405 22:41:15.832669 10376 out.go:296] Setting OutFile to fd 84 ...
I0405 22:41:15.833195 10376 out.go:343] TERM=,COLORTERM=, which probably does not support color
I0405 22:41:15.833195 10376 out.go:309] Setting ErrFile to fd 88...
I0405 22:41:15.833195 10376 out.go:343] TERM=,COLORTERM=, which probably does not support color
W0405 22:41:15.839489 10376 root.go:314] Error reading config file at C:\Users\User.minikube\config\config.json: open C:\Users\User.minikube\config\config.json: The system cannot find the file specified.
I0405 22:41:15.840018 10376 config.go:182] Loaded profile config "minikube": Driver=docker, ContainerRuntime=docker, KubernetesVersion=v1.28.3
I0405 22:41:15.840018 10376 localpath.go:146] windows sanitize: C:\Users\User.minikube\cache\images\amd64\kubernetes-test-app:latest -> C:\Users\User.minikube\cache\images\amd64\kubernetes-test-app_latest
I0405 22:41:15.900580 10376 cache.go:107] acquiring lock: {Name:mk4fcead5c2f30908233a6ee5532b61a8a1ec78b Clock:{} Delay:500ms Timeout:10m0s Cancel:}
I0405 22:41:15.901103 10376 image.go:134] retrieving image: kubernetes-test-app:latest
I0405 22:41:15.901103 10376 image.go:140] checking repository: index.docker.io/library/kubernetes-test-app
W0405 22:41:17.777959 10376 image.go:147] remote: HEAD https://index.docker.io/v2/library/kubernetes-test-app/manifests/latest: unexpected status code 401 Unauthorized (HEAD responses have no body, use GET for details)
I0405 22:41:17.777959 10376 image.go:148] short name: kubernetes-test-app:latest
I0405 22:41:17.783359 10376 image.go:173] found index.docker.io/library/kubernetes-test-app:latest locally: &{ref:{Repository:{Registry:{insecure:false registry:index.docker.io} repository:kubernetes-test-app} tag:latest original:kubernetes-test-app:latest} opener:0xc0009b2cb0 tarballImage: computed:false id:0xc00073e7a0 configFile: once:{done:0 m:{state:0 sema:0}} err:}
I0405 22:41:17.783359 10376 cache.go:162] opening: \?\Volume{00a1c5bd-e26d-407e-9da4-4f4c488bf51b}\Users\User.minikube\cache\images\amd64\kubernetes-test-app_latest
W0405 22:41:19.821405 10376 cache.go:173] failed to clean up the temp file \?\Volume{00a1c5bd-e26d-407e-9da4-4f4c488bf51b}\Users\User.minikube\cache\images\amd64\kubernetes-test-app_latest.1789695515.tmp: remove \?\Volume{00a1c5bd-e26d-407e-9da4-4f4c488bf51b}\Users\User.minikube\cache\images\amd64\kubernetes-test-app_latest.1789695515.tmp: The process cannot access the file because it is being used by another process.
I0405 22:41:19.821405 10376 cache.go:96] cache image "kubernetes-test-app:latest" -> "C:\Users\User\.minikube\cache\images\amd64\kubernetes-test-app_latest" took 3.9813874s
I0405 22:41:19.821405 10376 out.go:177]
W0405 22:41:19.822406 10376 out.go:239] X Exiting due to GUEST_IMAGE_LOAD: Failed to load image: save to dir: caching images: caching image "C:\Users\User\.minikube\cache\images\amd64\kubernetes-test-app_latest": write: unable to calculate manifest: blob sha256:4e4b4c647fc89b6328ca1647f8c5a54abe4a89873307bd76501f6dd20df57a4a not found
W0405 22:41:19.822406 10376 out.go:239] *
W0405 22:41:19.823405 10376 out.go:239] ╭──────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue. │
│ * Please also attach the following file to the GitHub issue: │
│ * - C:\Users\User\AppData\Local\Temp\minikube_image_4d5366ce9c8a35fd0068105b9e59d79d20329f7e_0.log │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────╯
I0405 22:41:19.823405 10376 out.go:177]
Log file created at: 2025/04/05 22:51:34
Running on machine: DESKTOP-3RI4QR8
Binary: Built with gc go1.21.3 for windows/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I0405 22:51:34.571198 12000 out.go:296] Setting OutFile to fd 84 ...
I0405 22:51:34.571712 12000 out.go:343] TERM=,COLORTERM=, which probably does not support color
I0405 22:51:34.571712 12000 out.go:309] Setting ErrFile to fd 88...
I0405 22:51:34.571712 12000 out.go:343] TERM=,COLORTERM=, which probably does not support color
W0405 22:51:34.578508 12000 root.go:314] Error reading config file at C:\Users\User.minikube\config\config.json: open C:\Users\User.minikube\config\config.json: The system cannot find the file specified.
I0405 22:51:34.579535 12000 config.go:182] Loaded profile config "minikube": Driver=docker, ContainerRuntime=docker, KubernetesVersion=v1.28.3
I0405 22:51:34.579554 12000 localpath.go:146] windows sanitize: C:\Users\User.minikube\cache\images\amd64\kubernetes-test-app:latest -> C:\Users\User.minikube\cache\images\amd64\kubernetes-test-app_latest
I0405 22:51:34.655078 12000 cache.go:107] acquiring lock: {Name:mk4fcead5c2f30908233a6ee5532b61a8a1ec78b Clock:{} Delay:500ms Timeout:10m0s Cancel:}
I0405 22:51:34.655078 12000 image.go:134] retrieving image: kubernetes-test-app:latest
I0405 22:51:34.655078 12000 image.go:140] checking repository: index.docker.io/library/kubernetes-test-app
W0405 22:51:36.551616 12000 image.go:147] remote: HEAD https://index.docker.io/v2/library/kubernetes-test-app/manifests/latest: unexpected status code 401 Unauthorized (HEAD responses have no body, use GET for details)
I0405 22:51:36.551616 12000 image.go:148] short name: kubernetes-test-app:latest
I0405 22:51:36.557598 12000 image.go:173] found index.docker.io/library/kubernetes-test-app:latest locally: &{ref:{Repository:{Registry:{insecure:false registry:index.docker.io} repository:kubernetes-test-app} tag:latest original:kubernetes-test-app:latest} opener:0xc000472070 tarballImage: computed:false id:0xc000b9cc60 configFile: once:{done:0 m:{state:0 sema:0}} err:}
I0405 22:51:36.557598 12000 cache.go:162] opening: \?\Volume{00a1c5bd-e26d-407e-9da4-4f4c488bf51b}\Users\User.minikube\cache\images\amd64\kubernetes-test-app_latest
W0405 22:51:37.936301 12000 cache.go:173] failed to clean up the temp file \?\Volume{00a1c5bd-e26d-407e-9da4-4f4c488bf51b}\Users\User.minikube\cache\images\amd64\kubernetes-test-app_latest.1762215162.tmp: remove \?\Volume{00a1c5bd-e26d-407e-9da4-4f4c488bf51b}\Users\User.minikube\cache\images\amd64\kubernetes-test-app_latest.1762215162.tmp: The process cannot access the file because it is being used by another process.
I0405 22:51:37.936301 12000 cache.go:96] cache image "kubernetes-test-app:latest" -> "C:\Users\User\.minikube\cache\images\amd64\kubernetes-test-app_latest" took 3.3567464s
I0405 22:51:37.936301 12000 out.go:177]
W0405 22:51:37.937302 12000 out.go:239] X Exiting due to GUEST_IMAGE_LOAD: Failed to load image: save to dir: caching images: caching image "C:\Users\User\.minikube\cache\images\amd64\kubernetes-test-app_latest": write: unable to calculate manifest: blob sha256:4e4b4c647fc89b6328ca1647f8c5a54abe4a89873307bd76501f6dd20df57a4a not found
W0405 22:51:37.937302 12000 out.go:239] *
W0405 22:51:37.938301 12000 out.go:239] ╭──────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue. │
│ * Please also attach the following file to the GitHub issue: │
│ * - C:\Users\User\AppData\Local\Temp\minikube_image_4d5366ce9c8a35fd0068105b9e59d79d20329f7e_0.log │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────╯
I0405 22:51:37.939305 12000 out.go:177]

Operating System

Windows

Driver

Docker

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

Details

In response to this:

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.