Upstream software project

krunvm

Manage lightweight VMs created from OCI images

About krunvm

Manage lightweight VMs created from OCI images

This project links 2 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

krunvm repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.krunvm: recorded package coverageopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
krunvm
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
opensuse-leap-16-0, 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.

Manage lightweight VMs created from OCI images

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 16.0

  1. Package krunvm

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Manage lightweight VMs created from OCI images

    0.2.3+git12dac81-bp160.1.13: aarch64 x86_64

    Source: krunvm

openSUSE Tumbleweed

  1. Package krunvm

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Manage lightweight VMs created from OCI images

    0.2.6+git59f3673-1.4: x86_64

    Source: krunvm

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.