Trying to import podman/v3/bindings/containers fails with github.com/containernetworking/cni/pkg/types/current: module github.com/containernetworking/cni@latest found (v1.1.2), but does not contain package github.com/containernetworking/cni/pkg/types/current

[thediveo]

In my project I need to use the v3 podman REST API client, as the target Debian and Ubuntu LTS systems will be at best have the distribution's own podman packages installed.

Trying to import github.com/containers/podman/v3/bindings/containers fails:

github.com/thediveo/whalewatcher/engineclient/podman imports
        github.com/containers/podman/v3/pkg/bindings/containers imports
        github.com/containers/podman/v3/pkg/domain/entities imports
        github.com/cri-o/ocicni/pkg/ocicni imports
        github.com/containernetworking/cni/pkg/types/current: module github.com/containernetworking/cni@latest found (v1.1.2), but does not contain package github.com/containernetworking/cni/pkg/types/current

Importing podman/v3/pkg/bindings/system and podman/v3/pkg/bindings seem to work.

How to deal with this? Is there some known pinning? Or will there be an v3 update that fixes this?

[thediveo]

git log --full-history -1 -- pkg/types/current gives:

commit d1e1ae3c3420242a378a918d6badf27a0c08492d
Merge: 6fc72a4 7555ca3
Author: Dan Williams <[email protected]>
Date:   Thu Nov 19 07:59:36 2020 -0600

    Merge pull request #783 from dcbw/100
    
    types changes for 1.0.0

[thediveo]

v3 API clients need explicit pinning:

go get github.com/containernetworking/[email protected]