Podman version mismatch

[bhunsicker]

What Happened?

Installed Podman on Windows 10 (v4.2)
installed Minikube

podman machine stop podman machine set --rootful podman machine start minikube config set driver podman minikube config set rootless false minikube config set container-runtime crio minikube config set insecure-registry docker-base-usaa.repo.usaa.com minikube config set embed-certs true copy the roo2GA to ~/.minikube/certs/ minikube start --network-plugin=cni --cni=auto --extra-config=kubelet.cgroup-driver=systemd --embed-certs kubectl config use-context minikube & minikube -p minikube podman-env --shell powershell | Invoke-Expression
try to run a podman build podman build . -t api-ecosystem-ref-app

get this error:
Error: unable to connect to Podman socket: server API version is too old. Client "4.0.0" server "3.4.2"

Any idea when minikube will upgrade the internal podman or instructions so I can do it myself?

Attach the log file

log file too long

Operating System

Windows

Driver

Podman

[afbjorklund]

It will have to wait until the Ubuntu version is upgraded (to 22.04)...

For now, you can install the older podman3 client for it.
https://github.com/containers/podman/releases/tag/v3.4.4

You can also use minikube image, instead of podman.

[bhunsicker]

yea, that was my workaround. it has been ... interesting :)

Thanks!

[mnebus]

Any updates on this?

[afbjorklund]

Probably just remove the podman support (for remote), though you can still use minikube ssh and minikube image.

• Deprecate "podman-env", in favor of using "docker-env" with cri-o #15461

There was some idea to update the 3.4.2 to something like 3.4.4 or 3.4.7, but I don't think anyone started on 4.x ?

The external driver should probably support it, though. Or only Podman Desktop.

[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

[phvogtrbi]

I would really be interested in an update, as RHEL 9 provides podman > 4.x and therefore minikube cannot really be used together with podman built images.

[afbjorklund]

Why are the images depending on the podman version ? It does need an older podman-remote client, but that's a different story. Minikube only needs something that can talk to the cri-o image store, and podman3 can do that.

[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".

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/test-infra repository.