-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
"kind load" tries to call docker though podman is used as runtime #2760
Comments
This is only true for "kind load docker-image" which yes that uses docker. See discussion in #2729 |
I see.. thx for the quick answer! I'm fine with a symlink or image file pipe until #2729 is realized. |
I would love to see #2038 to add a new command dropping docker from the name and supporting all the inputs, I don't think it's super challenging, but there's just so many critical things (bug fixes...) to do between this project and elsewhere in kubernetes that nobody seems to have gotten to it yet. |
Hm now this is strange
Don't know how the image-archive transfer (which works fine if fed by a real file instead of a pipe) is realized internally... seems ctr behaves differently when writing to / reading from a pipe. |
Maybe it's defaulting |
Don't know... the same error occurs regardless whether I call
|
We save to a tempdir and then pipe in that file with go kind/pkg/cmd/kind/load/docker-image/docker-image.go Lines 149 to 158 in c8b759f
I don't know why podman would be different here. It is equivalent to |
@mheon @vrothberg does this ring any bell? why should podman have a different behavior piping the images? |
Thanks for the ping, @aojea! Can you share a reproducer? I see a number of issues in this thread and am not sure which one to pick. In theory, there should be no difference when piping. |
What happened:
kind load
fails (with a misleading error message about the image not being available locally) if podman is used as runtime,because it tries to do image management by calling a binary called "docker"
What you expected to happen:
If the cluster is provisioned by using podman as runtime management tool, kind should also call the podman bnary for image
management on load operations
How to reproduce it (as minimally and precisely as possible):
KIND_EXPERIMENTAL_PROVIDER=podman
as environment variableThis provokes an error
Environment:
kind version
): v0.13kubectl version
): v1.24.0docker info
): none -- but podman v3.4.7 and v4.1.1 work fine/etc/os-release
): Fedora 35 SilverblueThe text was updated successfully, but these errors were encountered: