Minikube podman-env does not work with podman 3.1

[VeitSanner]

Steps to reproduce the issue:

1. Execute eval $(minikube -p minikube podman-env).
2. Execute podman-remote build -t example:latest .

Full output of failed command if not minikube start:

Error: cannot connect to the Podman socket, please verify that Podman REST API service is running: server API version is too old. Client "3.1.0" server "2.0.0"

Operating System: macOS 11.6

Podman Version:

Client:
Version:      3.3.1
API Version:  3.3.1
Go Version:   go1.17
Built:        Mon Aug 30 21:15:26 2021
OS/Arch:      darwin/amd64

minikube version

minikube version: v1.23.0
commit: 5931455374810b1bbeb222a9713ae2c756daee10

[afbjorklund]

You need to install the older podman-remote version, or run podman over ssh, until the podman version has been updated (PR #11727)

Podman is not backwards compatible, so you need to have multiple clients (podman1, podman2, podman3, podman4 etc)

[afbjorklund]

You can also use minikube image build instead.

[dilyanpalauzov]

You could try podman --remote instead of podman-remote.

[afbjorklund]

You could try podman --remote instead of podman-remote.

That would have the same effect, but could be a good idea anyway.

Hopefully the podman-remote binary will go away in the future, and the --remote flag will be automatic.
Right now it is needed on Linux, but not on macOS/Windows. Which makes instructions rather confusing.

[afbjorklund]

Anyway, the needed podman client binaries can be downloaded here:

https://github.com/containers/podman/releases/tag/v2.2.1

• podman-remote-release-darwin.zip
• podman-remote-release-windows.zip
• podman-remote-static.tar.gz (linux)

[dilyanpalauzov]

I mean, the user might have different versions behind podman-remote and podman.

[VeitSanner]

I have installed podman and podman-remote via brew. So both binaries are fairly up-to-date with versions 3.3.1.

As far as I can see, PR #11727 seems to be pretty close to be complete. Is there an ETA when the fix would be available?

Until then I can work with minikube image build.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale