Upstream software project

container-support-utils

Open a shell inside a running container

About container-support-utils

Open a shell inside a running container

This project links 1 native package record across 1 recorded operating-system release. 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

container-support-utils repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.container-support-utils: recorded package coverageopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
container-support-utils
Publisher
Not authoritatively mapped
Native package records
1
Operating systems
opensuse-tumbleweed
License expression
GPL-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.

This utility allows you to run a shell, and use diagnostic utilities, inside an already running container. The main purpose of this is problem diagnosis.

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 Tumbleweed

  1. Package container-support-utils

    tumbleweed (openSUSE Tumbleweed) (System/Packages): Open a shell inside a running container

    0.2.2-1.24: x86_64

    Source: container-support-utils

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.