aardvark-dns
- Ebuilds: 3, Stable: 1.17.0, Testing: 9999 Description:
Aardvark-dns is an authoritative dns server for A/AAAA container
records. It can forward other requests to configured resolvers.
Homepage:https://github.com/containers/aardvark-dns License: 0BSD Apache-2.0-with-LLVM-exceptions MIT Unlicense Unicode-DFS-2016 ZLIB
containerd
- Ebuilds: 11, Stable: 2.1.4, Testing: 2.2.1 Description:
Containerd is a daemon with an API and a command line client, to manage
containers on one machine. It uses runC to run containers according to
the OCI specification. Containerd has advanced features such as seccomp
and user namespace support as well as checkpoint and restore for cloning
and live migration of containers.
Homepage:https://containerd.io/ License: Apache-2.0
cri-o
- Ebuilds: 3, Testing: 1.34.3 Description:
CRI-O is meant to provide an integration path between
OCI conformant runtimes and the kubelet. Specifically, it
implements the Kubelet Container Runtime Interface (CRI)
using OCI conformant runtimes. The scope of CRI-O is tied to
the scope of the CRI.
Homepage:https://cri-o.io/ License: Apache-2.0 BSD BSD-2 CC-BY-SA-4.0 ISC MIT MPL-2.0
cri-tools
- Ebuilds: 3, Stable: 1.33.0, Testing: 1.33.0 Description: CLI and validation tools for Kubelet Container Runtime (CRI)
Homepage:https://github.com/kubernetes-sigs/cri-tools License: Apache-2.0 BSD BSD-2 CC-BY-SA-4.0 ISC MIT MPL-2.0
crun
- Ebuilds: 4, Stable: 1.21, Testing: 1.25.1 Description:
While most of the tools used in the Linux containers ecosystem are written in
Go, crun authors believe C is a better fit for a lower level tool like a
container runtime. runc; the most used implementation of the OCI runtime specs
written in Go, re-execs itself and use a module written in C for setting up
the environment before the container process starts.
crun aims to be also usable as a library that can be easily included in
programs without requiring an external process for managing OCI containers.
Homepage:https://github.com/containers/crun
devcontainer
- Ebuilds: 4, Stable: 0.81.1, Testing: 0.84.1 Description:
A Development Container (or Dev Container for short) allows you to use a
container as a full-featured development environment. It can be used to run
an application, to separate tools, libraries, or runtimes needed for
working with a codebase, and to aid in continuous integration and testing.
Dev containers can be run locally or remotely, in a private or public
cloud, in a variety of supporting tools and editors.
Homepage:https://containers.dev/
https://github.com/devcontainers/cli/ License: MIT
distrobox
- Ebuilds: 4, Stable: 1.8.2.3, Testing: 9999 Description:
Use any Linux distribution inside your terminal. Enable both backward and
forward compatibility with software and freedom to use whatever
distribution you’re more comfortable with. Distrobox uses podman or docker
to create containers using the Linux distribution of your choice. The
created container will be tightly integrated with the host, allowing
sharing of the HOME directory of the user, external storage, external USB
devices and graphical apps (X11/Wayland), and audio.
Homepage:https://distrobox.it/
https://github.com/89luca89/distrobox/
dive
- Ebuilds: 1, Testing: 0.13.1 Description: terminal based UI to manage kubernetes clusters
Homepage:https://github.com/wagoodman/dive License: MIT
docker
- Ebuilds: 6, Stable: 28.2.2, Testing: 29.1.3-r1 Description:
Docker is an open-source project to easily create lightweight,
portable, self-sufficient containers from any application. The same
container that a developer builds and tests on a laptop can run at
scale, in production, on VMs, bare metal, OpenStack clusters, public
clouds and more.
Homepage:https://www.docker.com/ License: Apache-2.0
docker-bench-security
- Ebuilds: 2, Testing: 1.6.1 Description:
The Docker Bench for Security is a script that checks for dozens of
common best-practices around deploying Docker containers in production.
Homepage:https://github.com/docker/docker-bench-security License: Apache-2.0
docker-buildx
- Ebuilds: 6, Stable: 0.21.2, Testing: 9999 Description:
buildx is a Docker CLI plugin for extended build capabilities with BuildKit.
BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.
Homepage:https://github.com/docker/buildx License: Apache-2.0 BSD BSD-2 ISC MIT MPL-2.0
docker-cli
- Ebuilds: 6, Stable: 28.4.0, Testing: 29.1.3 Description: the command line binary for docker
Homepage:https://www.docker.com/ License: Apache-2.0
docker-credential-helpers
- Ebuilds: 3, Stable: 0.9.3 Description:
A suite of programs to use native stores to keep Docker credentials
safe. Currently provides docker-credential-secretservice to use the
D-Bus secret service APIs, and docker-credential-pass to use the
pass framework.
Homepage:https://github.com/docker/docker-credential-helpers License: MIT
docker-pushrm
- Ebuilds: 1, Testing: 1.9.0 Description:
docker-pushrm is a Docker CLI plugin that adds a new docker pushrm
command to Docker. It pushes the README file from the current working
directory to a container registry server where it appears as repo
description in the web interface. It currently supports Docker Hub, Red
Hat Quay and Harbor v2. For most registry types docker-pushrm uses
authentication info from the Docker credentials store - so it "just
works" for registry servers that you're already logged into with Docker.
Homepage:https://github.com/docker/buildx License: MIT
docker-swarm
- Ebuilds: 1, Testing: 1.2.9 Description: Swarm Classic: a container clustering system
Homepage:https://docs.docker.com/swarm License: Apache-2.0 CC-BY-SA-4.0 BSD BSD-2 ISC MIT MPL-2.0 WTFPL-2
earthly
- Ebuilds: 1, Stable: 0.8.16, Testing: 0.8.16 Description:
Earthly is a versatile, approachable CI/CD framework that runs every
pipeline inside containers, giving you repeatable builds that you write
once and run anywhere. It has a super simple, instantly recognizable syntax
that is easy to write and understand – like Dockerfile and Makefile had a
baby. And it leverages and augments popular build tools instead of
replacing them, so you don’t have to rewrite all your builds no matter what
languages you use.
Homepage:https://earthly.dev/
https://github.com/earthly/earthly/ License: MPL-2.0
flannel
- Ebuilds: 1, Testing: 0.26.3 Description: An etcd backed network fabric for containers
Homepage:https://github.com/flannel-io/flannel License: Apache-2.0 BSD ISC LGPL-3 MIT
grype
- Ebuilds: 6, Testing: 0.86.1 Description: A vulnerability scanner for container images and filesystems
Homepage:https://www.anchore.com License: Apache-2.0
img
- Ebuilds: 1, Testing: 0.5.11 Description: Standalone daemon-less unprivileged Dockerfile and OCI container image builder
Homepage:https://github.com/genuinetools/img License: MIT
incus
- Ebuilds: 5, Stable: 6.0.5-r1, Testing: 9999 Description:
Incus is a modern, secure and powerful system container and virtual machine manager.
Incus is a community fork from Canonical's LXD.
It provides a unified experience for running and managing full Linux systems inside containers
or virtual machines. Incus supplies images for a wide number of Linux distributions and is built
around a very powerful, yet pretty simple, REST API. Incus scales from one instance on a single
machine to a cluster in a full data center rack, making it suitable for running workloads both
for development and in production.
Incus allows you to easily set up a system that feels like a small private cloud. You can run any
type of workload in an efficient way while keeping your resources optimized.
You should consider using Incus if you want to containerize different environments or run virtual
machines, or in general run and manage your infrastructure in a cost-effective way.
Homepage:https://linuxcontainers.org/incus/introduction/ https://github.com/lxc/incus License: Apache-2.0 BSD LGPL-3 MIT
lxd
- Ebuilds: 4, Stable: 5.21.1-r1, Testing: 6.5 Description:
LXD is a modern, secure and powerful system container and virtual machine manager.
It provides a unified experience for running and managing full Linux systems inside containers
or virtual machines. LXD supplies images for a wide number of Linux distributions and is built
around a very powerful, yet pretty simple, REST API. LXD scales from one instance on a single
machine to a cluster in a full data center rack, making it suitable for running workloads both
for development and in production.
LXD allows you to easily set up a system that feels like a small private cloud. You can run any
type of workload in an efficient way while keeping your resources optimized.
You should consider using LXD if you want to containerize different environments or run virtual
machines, or in general run and manage your infrastructure in a cost-effective way.
Homepage:https://ubuntu.com/lxd https://github.com/canonical/lxd License: Apache-2.0 AGPL-3+ BSD LGPL-3 MIT
nerdctl
- Ebuilds: 3, Testing: 2.2.1 Description: Docker-compatible CLI for containerd, with support for Compose
Homepage:https://github.com/containerd/nerdctl License: Apache-2.0 BSD BSD-2 ISC MIT
netavark
- Ebuilds: 6, Stable: 1.17.1, Testing: 9999 Description:
Netavark is a rust based network stack for containers. It is
being designed to work with Podman but is also applicable for
other OCI container management applications.
Homepage:https://github.com/containers/netavark License: Apache-2.0-with-LLVM-exceptions BSD BSD-2 Boost-1.0 MIT Unicode-DFS-2016 Unlicense ZLIB
nvidia-container-toolkit
- Ebuilds: 4, Stable: 1.18.0, Testing: 9999 Description:
NVIDIA container runtime toolkit, build and run containers leveraging
NVIDIA GPUs. tl;dr: nvidia-docker is deprecated because docker now has
native gpu support, which this package is required to use. The NVIDIA
Container Toolkit (formerly known as NVIDIA Docker) allows containers to
access full GPU acceleration. OpenGL, OpenCL and CUDA are supported for
production use. Vulkan support is currently in beta. This only works for
Linux containers running on Linux host systems with NVIDIA GPUs.
Homepage:https://github.com/NVIDIA/container-toolkit
podman
- Ebuilds: 3, Stable: 5.7.1, Testing: 9999 Description:
Podman (the POD MANager) is a tool for managing containers
and images, volumes mounted into those containers, and pods
made from groups of containers. Podman is based on libpod,
a library for container lifecycle management that is also
contained in this repository. The libpod library provides
APIs for managing containers, pods, container images,
and volumes.
Homepage:https://github.com/containers/podman/ https://podman.io/ License: BSD BSD-2 CC-BY-SA-4.0 ISC MIT MPL-2.0
runc
- Ebuilds: 8, Stable: 1.3.3, Testing: 1.4.0-r1 Description:
runc is a CLI tool for spawning and running containers according
to the OCF (Open Container Format) specification.
Homepage:https://github.com/opencontainers/runc/ License: Apache-2.0 BSD-2 BSD MIT
snapd
- Ebuilds: 1, Stable: 2.63 Description: Service and tools for management of snap packages
Homepage:http://snapcraft.io/ License: GPL-3 Apache-2.0 BSD BSD-2 LGPL-3-with-linking-exception MIT
syft
- Ebuilds: 6, Testing: 1.18.1 Description: Generate a Software Bill of Materials from container images and filesystems
Homepage:https://www.anchore.com License: Apache-2.0