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

Feature request: Minikube image load - progress bar #20103

Open
stianteien opened this issue Dec 14, 2024 · 2 comments
Open

Feature request: Minikube image load - progress bar #20103

stianteien opened this issue Dec 14, 2024 · 2 comments
Labels
area/image Issues/PRs related to the minikube image subcommand kind/feature Categorizes issue or PR as related to a new feature.

Comments

@stianteien
Copy link

stianteien commented Dec 14, 2024

What Happened?

When loading my local image into minikube it is often larger images that takes some time. It will amazing if I can get some kind of progress bar for the loading. I am sitting 10+ minutes wondering if there is some issues..
It is possible to see in "docker stats" under the I/O of system. But would like it in minikube command :)

Attach the log file

minikube image load "my-image"
[######-------------] 39%

Operating System

macOS (Default)

Driver

Docker

@afbjorklund
Copy link
Collaborator

afbjorklund commented Dec 15, 2024

With the current API there is no means in which to provide progress, so you would have to use a docker client.

        // Load an image idempotently into the runtime on a host
        LoadImage(string) error
        // Pull an image to the runtime from the container registry
        PullImage(string) error
        // Build an image idempotently into the runtime on a host
        BuildImage(string, string, string, bool, []string, []string) error
        // Save an image from the runtime on a host
        SaveImage(string, string) error
        // Tag an image
        TagImage(string, string) error
        // Push an image from the runtime to the container registry
        PushImage(string) error

That is, first do minikube docker-env to set up the host and then do docker load to get better progress report.

@afbjorklund afbjorklund added area/image Issues/PRs related to the minikube image subcommand kind/feature Categorizes issue or PR as related to a new feature. labels Dec 15, 2024
@afbjorklund
Copy link
Collaborator

afbjorklund commented Dec 15, 2024

If you are running an external docker daemon, you would have to juggle the environment for each one.

$ docker save python | ( eval $(minikube docker-env); docker load )
301c1bb42cc0: Loading layer [==================================================>]  121.4MB/121.4MB
0e82d78b3ea1: Loading layer [==================================================>]  48.82MB/48.82MB
c81d4fdb67fc: Loading layer [==================================================>]  181.9MB/181.9MB
0aeeeb7c293d: Loading layer [==================================================>]  597.1MB/597.1MB
1d07cc98ca13: Loading layer [==================================================>]  18.36MB/18.36MB
315d5ede9617: Loading layer [==================================================>]  71.75MB/71.75MB
e5012203d367: Loading layer [==================================================>]   5.12kB/5.12kB
Loaded image: python:latest

Minikube offers several ways to do faster iteration of updating images, while "save | load" is the slowest.

https://minikube.sigs.k8s.io/docs/handbook/pushing/

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 kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants