Skip to content
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

Fix podman 5.0 unmarshall error. #332

Merged
merged 1 commit into from
Apr 15, 2024
Merged

Conversation

hbsnmyj
Copy link
Contributor

@hbsnmyj hbsnmyj commented Mar 31, 2024

Podman 5.0 introduces some inspect API type changes: commit, breaking the unmarshal code. Since we don't use the fields, we just delete them. See Issue #331.

Testing:

Note:

  • libpod has just implemented a compatible unmarshal API here.

New Podman 5.0 API: containers/podman@de845a5.
Upstream has an unmarshal API implementation: containers/podman@585af03.
@hashicorp-cla
Copy link

hashicorp-cla commented Mar 31, 2024

CLA assistant check
All committers have signed the CLA.

@torrancew
Copy link

It would be great to get this merged, it appears to be breaking Archlinux Nomad+Podman 5.0 deployments

@shoenig shoenig merged commit 419b7b5 into hashicorp:main Apr 15, 2024
2 checks passed
@skoppe
Copy link

skoppe commented May 28, 2024

Time for a new release?

lukaszo pushed a commit to koyeb/nomad-driver-podman that referenced this pull request Jun 4, 2024
New Podman 5.0 API: containers/podman@de845a5.
Upstream has an unmarshal API implementation: containers/podman@585af03.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants