4 个仓库
Pre-start mechanisms that inject drivers and libraries into container environments during creation.
Distinct from Dependency Injection Containers: Distinct from Dependency Injection Containers: focuses on container lifecycle hooks for hardware integration rather than application-level dependency management.
Explore 4 awesome GitHub repositories matching software engineering & architecture · Container Runtime Hooks. Refine with filters or upvote what's useful.
NVIDIA Docker is a container runtime wrapper that enables the use of host-level graphics processing units within isolated container environments. It functions as a containerized GPU orchestrator, mapping physical hardware resources into virtualized environments to support high-performance computing and machine learning workloads. The project provides a toolkit that facilitates integration between containerized applications and host-level graphics hardware. By utilizing a pre-start hook to intercept container creation, the runtime injects necessary device drivers and libraries into the isolate
Provides pre-start hooks that inject necessary host drivers and libraries into isolated container environments.
CRI-O is an open-source container runtime that implements the Kubernetes Container Runtime Interface (CRI) to manage container images, pods, and containers on cluster nodes using OCI-compatible runtimes. It serves as a node-level container manager that handles image pulling, container lifecycle, and resource monitoring for Kubernetes clusters, running containers according to the Open Container Initiative specifications. The runtime distinguishes itself through live configuration reloading that applies changes to runtime definitions, registry mirrors, and TLS certificates without restarting th
Injects OCI-compliant hooks during container creation to extend runtime behavior.
The project provides an open container runtime specification and standardized schema for defining container configurations, namespaces, resource limits, security policies, and filesystem mounts across platforms. It outlines the formal configuration formats, lifecycle operations, and execution environments necessary for portable, isolated container workloads. The specification covers container lifecycle management protocols and structured rules governing container creation, execution startup, process signaling, state tracking, and resource teardown. It standardizes local bundle packaging and
Enumerates recognized names of lifecycle hooks supported for container execution.
Sysbox is an OCI-compliant container runtime that provides virtual-machine-level isolation for containers without requiring hardware virtualization. It achieves this by mapping the container's root user to an unprivileged host user ID range, virtualizing the /proc and /sys filesystems, and applying seccomp-BPF system call filtering, all while using cgroup v2 for resource partitioning. The runtime enables running system-level software such as systemd, Docker, and Kubernetes inside unprivileged containers without requiring special images or privileged mode. It supports nested namespace stacking
Injects custom logic at container lifecycle events to configure namespaces, cgroups, and mounts.