podman-env update from <=3 to 4.9.2+

[elasticdotventures]

see issue #21052

[linux-foundation-easycla]

• ✅login: elasticdotventures / (8bfb441)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: elasticdotventures
Once this PR has been reviewed and has the lgtm label, please assign prezha for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @elasticdotventures!

It looks like this is your first PR to kubernetes/minikube 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/minikube has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @elasticdotventures. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[minikube-bot]

Can one of the admins verify this patch?

[afbjorklund]

The version 4.9.2 is quite specific, it might as well say 4.x (which is not supported anyway) and later (5.x)

https://endoflife.date/podman

[nirs]

Can we use latest podman (5.5) instead of a random old version?

[afbjorklund]

I don't think 4.9.3 is random*, but upgrading the client is not an issue.
Some people have problems with downgrading, but that's different.

* it is the "last" common v4 version, just like 1.9.3 was the last v1 version.
We could upgrade to v5, but it is not available in every distribution yet.

[afbjorklund]

There are no features in podman 5 (or even in podman 4, but anyway)
that are required by cri-o, as far as I know? Main issue is client compat.

For the podman driver things are different, there we can require 4.9
This was just for docker-env/podman-env, and what is installed on the VM

[medyagh]

can you plz post before/after this PR in the description

[afbjorklund]

I don't think we should look for podman, or suggest to people to use the podman --remote client. We should only give a path to a docker socket, for a docker client.

Podman Desktop does not use podman, and Podman Compose does not default to using podman-compose. Instead, they use the Docker API and docker-compose.

Using the podman-remote client, is what is causing these problems with using cri-o.

Error: unable to connect to Podman socket: server API version is too old. Client "4.0.0" server "3.4.4"

It is better to only use docker as a legacy client, and minikube image for the rest.

That is why it is called "compatibility socket", while the libpod client/connection keeps breaking the backwards API...