Skip to content

port podman over to new moby/moby module instead of the old docker/docker one #27536

@Luap99

Description

@Luap99

Image was already moved in containers/container-libs#459

We do vendor update it in #27342 which broke swagger so I did a quick fix in 6f9bf07 for that to unblock vendoring.

However we need someone to port all the types to use the moby modules in podman so the docker module will get dropped.


On another note to we actually benifit from reusing the docker/moby types instead of having our own definitions? All the past updates were quite painful as they keep moving things around so we already spend a ton of work on these changes. And in practice it doesn't gain much, like just because they add new field it still doesn't mean it works in podman becuase podman of course still has to actually populate these fields with our data to return them in the API.
And right now we still do not properly track and implement the new docker API changes so these updates are not helping for that either.

Metadata

Metadata

Assignees

No one assigned

    Labels

    6.0Breaking changes for Podman 6.0kind/featureCategorizes issue or PR as related to a new feature.triagedIssue has been triaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions