Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minikube Image Load process is killed without loading docker image #17983

Open
lucian-cap opened this issue Jan 18, 2024 · 3 comments
Open

Minikube Image Load process is killed without loading docker image #17983

lucian-cap opened this issue Jan 18, 2024 · 3 comments
Labels
area/image Issues/PRs related to the minikube image subcommand lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@lucian-cap
Copy link

lucian-cap commented Jan 18, 2024

What Happened?

Executing the minikube image load command to load a locally built image into the container runtime in the cluster leads to the process being killed. The container is quite large (16.2GB) but if I use the Docker daemon in the minikube cluster via eval $(minikube docker-env) and build the images then everything works just fine.

I am running Windows 11 with WSL2 (Ubuntu 22.04), using Docker Engine installed in WSL,

Logs included below:
`I0118 07:29:38.907328 113509 out.go:296] Setting OutFile to fd 1 ...

I0118 07:29:38.907697 113509 out.go:348] isatty.IsTerminal(1) = true

I0118 07:29:38.907715 113509 out.go:309] Setting ErrFile to fd 2...

I0118 07:29:38.907727 113509 out.go:348] isatty.IsTerminal(2) = true

I0118 07:29:38.907828 113509 root.go:338] Updating PATH: /home/lucian/.minikube/bin

I0118 07:29:38.910323 113509 config.go:182] Loaded profile config "minikube": Driver=docker, ContainerRuntime=docker, KubernetesVersion=v1.28.3

I0118 07:29:38.910645 113509 cache.go:107] acquiring lock: {Name:mk9d2423cbb3b42e30b10267c78183a202fa4c2a Clock:{} Delay:500ms Timeout:10m0s Cancel:}

I0118 07:29:38.911163 113509 image.go:134] retrieving image: triton-server:latest

I0118 07:29:38.911185 113509 image.go:140] checking repository: index.docker.io/library/triton-server
W0118 07:29:39.317577 113509 image.go:147] remote: HEAD https://index.docker.io/v2/library/triton-server/manifests/latest: unexpected status code 401 Unauthorized (HEAD responses have no body, use GET for details)

I0118 07:29:39.317613 113509 image.go:148] short name: triton-server:latest

I0118 07:29:39.402658 113509 image.go:173] found index.docker.io/library/triton-server:latest locally: &{ref:{Repository:{Registry:{insecure:false registry:index.docker.io} repository:triton-server} tag:latest original:triton-server:latest} opener:0xc0004477a0 tarballImage: computed:false id:0xc000439260 configFile: once:{done:0 m:{state:0 sema:0}} err:}

I0118 07:29:39.402694 113509 cache.go:162] opening: /home/lucian/.minikube/cache/images/amd64/triton-server_latest

Killed`

Attach the log file

log.txt

Operating System

Other

Driver

Docker

@afbjorklund
Copy link
Collaborator

Try saving the image to a file first (docker save), there are some issues with creating the tarball with minikube.

@afbjorklund afbjorklund added the area/image Issues/PRs related to the minikube image subcommand label Jan 18, 2024
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 17, 2024
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/image Issues/PRs related to the minikube image subcommand lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants