Upstream software project

golang-github-containernetworking-plugins

Container Network Interface plugins

About golang-github-containernetworking-plugins

Container Network Interface plugins

This project links 10 native package records across 6 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

golang-github-containernetworking-plugins repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 2 package records; Debian 13 (Trixie): 2 package records; Fedora 43: 2 package records; Fedora 44: 2 package records; openSUSE Leap 15.6: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.golang-github-containernetworking-plugins: recorded package coverageDebian 12 (Bookworm)2 recordsDebian 13 (Trixie)2 recordsFedora 432 recordsFedora 442 recordsopenSUSE Leap 15.61 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
golang-github-containernetworking-plugins
Publisher
Not authoritatively mapped
Native package records
10
Operating systems
debian-12, debian-13, fedora-43, fedora-44, opensuse-leap-15-6, opensuse-tumbleweed
License expression
Apache-2.0
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support and the specification is simple to implement. These are the additional CNI network plugins provided by the containernetworking team.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. Package containernetworking-plugins

    bookworm (Debian 12 (Bookworm)) (devel): standard networking plugins - binaries

    1.1.1+ds1-3+b5: amd64 arm64

    Source: golang-github-containernetworking-plugins

  2. Source: golang-github-containernetworking-plugins

Debian 13 (Trixie)

  1. Package containernetworking-plugins

    trixie (Debian 13 (Trixie)) (devel): standard networking plugins - binaries

    1.1.1+ds1-3+b17: amd64 arm64

    Source: golang-github-containernetworking-plugins

  2. Source: golang-github-containernetworking-plugins

Fedora 43

  1. Package containernetworking-plugins

    43 (Fedora 43) (Unspecified): Reference and example networking plugins, maintained by the CNI team

    1.9.1-5.fc43: aarch64 x86_64

    Source: containernetworking-plugins

  2. Source: golang-github-containernetworking-plugins

Fedora 44

  1. Package containernetworking-plugins

    44 (Fedora 44) (Unspecified): Reference and example networking plugins, maintained by the CNI team

    1.9.1-5.fc44: aarch64 x86_64

    Source: containernetworking-plugins

  2. Source: golang-github-containernetworking-plugins

openSUSE Leap 15.6

  1. Package cni-plugins

    leap-15.6 (openSUSE Leap 15.6) (System/Management): Container Network Interface plugins

    1.1.1-150500.3.2.1: aarch64 ppc64le s390x x86_64

    Source: cni-plugins

openSUSE Tumbleweed

  1. Package cni-plugins

    tumbleweed (openSUSE Tumbleweed) (System/Management): Container Network Interface plugins

    1.6.2-1.8: x86_64

    Source: cni-plugins

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.