-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
when host has podman from podman-next and podman-remote is run inside a toolbox : unmarshalling error #22657
Comments
This looks like a client/server mismatch. We made some breaking changes to |
Mmm right, I tried installing I was thinking that maybe some nice stderr message of version mismatch would be more polite to the user, but only if the plan is to support different |
Version mismatch message does seem like a good idea, especially for a major version mismatch - we know that 4.x and 5.x will have incompatibilities when used together |
I think we explicitly didn't want the version check as almost all endpoints work normal. Only inspect was changed. IMO as I commented on the PR instead of blocking outright we should rather do the work and on a v4 request return the v4 payload. |
The v5 API made a breaking change for podman inspect, this means that an old client could not longer parse the result from the new 5.X server. The other way around new client and old server already worked. As it turned out there were several users that run into this, one case to hit this is using an old 4.X podman machine wich now pulls a newer coreos with podman 5.0. But there are also other users running into it. In order to keep the API working we now have a version check and return the old v4 compatible payload so the old remote client can still work against a newer server thus removing any major breaking change for an old client. Fixes containers#22657 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
The v5 API made a breaking change for podman inspect, this means that an old client could not longer parse the result from the new 5.X server. The other way around new client and old server already worked. As it turned out there were several users that run into this, one case to hit this is using an old 4.X podman machine wich now pulls a newer coreos with podman 5.0. But there are also other users running into it. In order to keep the API working we now have a version check and return the old v4 compatible payload so the old remote client can still work against a newer server thus removing any major breaking change for an old client. Fixes containers#22657 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Issue Description
I was trying to reproduce the issue #21974 which is valid for podman < 5 (did not bisect, take this with a grain of salt).
I realized that having podman installed from podman next leads to an error.
Steps to reproduce the issue
Steps to reproduce the issue
podman-remote run
podman-remote run --cidfile /var/tmp/cidfile fedora:latest true
in the toolboxDescribe the results you received
Describe the results you expected
Command should work
podman info output
The text was updated successfully, but these errors were encountered: