Upstream software project

libcontainers-common

Add SUSE and openSUSE registries to be used to pull images along with dockerhub

About libcontainers-common

Add SUSE and openSUSE registries to be used to pull images along with dockerhub

This project links 11 native package records across 2 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

openSUSE Leap 15.6: 6 package records; openSUSE Leap 16.0: 5 package records. Catalog coverage diagram, not an application screenshot.libcontainers-common: recorded package coverageopenSUSE Leap 15.66 recordsopenSUSE Leap 16.05 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
libcontainers-common
Publisher
Not authoritatively mapped
Native package records
11
Operating systems
opensuse-leap-15-6, opensuse-leap-16-0
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.

Configuration files and manpages shared by tools that are based on the github.com/containers libraries, such as Buildah, CRI-O, Podman and Skopeo.

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.

openSUSE Leap 15.6

  1. Package libcontainers-common

    leap-15.6 (openSUSE Leap 15.6) (System/Management): Configuration files common to github.com/containers

    20240408-150600.1.1: noarch

    Source: libcontainers-common

  2. Package libcontainers-default-policy

    leap-15.6 (openSUSE Leap 15.6) (System/Management): Default containers policy.json

    20240408-150600.1.1: noarch

    Source: libcontainers-common

  3. Package libcontainers-openSUSE-policy

    leap-15.6 (openSUSE Leap 15.6) (System/Management): Policy to enforce image verification for SLE BCI

    20240408-150600.1.1: noarch

    Source: libcontainers-common

  4. Package libcontainers-sles-mounts

    leap-15.6 (openSUSE Leap 15.6) (System/Management): Default mounts for SLE distributions

    20240408-150600.1.1: noarch

    Source: libcontainers-common

  5. Package registries-conf-default

    leap-15.6 (openSUSE Leap 15.6) (System/Management): Add SUSE and openSUSE registries to be used to pull images along with dockerhub

    20240408-150600.1.1: noarch

    Source: libcontainers-common

  6. Package registries-conf-suse

    leap-15.6 (openSUSE Leap 15.6) (System/Management): Defaults to SUSE Registry on SL Micro

    20240408-150600.1.1: noarch

    Source: libcontainers-common

openSUSE Leap 16.0

  1. Package libcontainers-common

    leap-16.0 (openSUSE Leap 16.0) (System/Management): Configuration files common to github.com/containers

    20250409-160000.2.2: noarch

    Source: libcontainers-common

  2. Package libcontainers-default-policy

    leap-16.0 (openSUSE Leap 16.0) (System/Management): Default containers policy.json

    20250409-160000.2.2: noarch

    Source: libcontainers-common

  3. Package libcontainers-openSUSE-policy

    leap-16.0 (openSUSE Leap 16.0) (System/Management): Policy to enforce image verification for SLE BCI

    20250409-160000.2.2: noarch

    Source: libcontainers-common

  4. Package registries-conf-default

    leap-16.0 (openSUSE Leap 16.0) (System/Management): Add SUSE and openSUSE registries to be used to pull images along with dockerhub

    20250409-160000.2.2: noarch

    Source: libcontainers-common

  5. Package registries-conf-suse

    leap-16.0 (openSUSE Leap 16.0) (System/Management): Defaults to SUSE Registry on SL Micro

    20250409-160000.2.2: noarch

    Source: libcontainers-common

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.