awesome-repositories.com
Blog
MCP
awesome-repositories.com

Découvrez les meilleurs dépôts open-source grâce à notre recherche par IA.

ExplorerRecherches sélectionnéesAlternatives open sourceLogiciels auto-hébergésBlogPlan du site
ProjetServeur MCPÀ proposNotre méthodologiePresse
Mentions légalesConfidentialitéConditions d'utilisation
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·

4 dépôts

Awesome GitHub RepositoriesContainer Runtime Hooks

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.

Awesome Container Runtime Hooks GitHub Repositories

Trouvez les meilleurs dépôts grâce à l'IA.Nous recherchons les dépôts les plus pertinents grâce à l'IA.
  • nvidia/nvidia-dockerAvatar de NVIDIA

    NVIDIA/nvidia-docker

    17,496Voir sur GitHub↗

    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.

    cudadockergpu
    Voir sur GitHub↗17,496
  • cri-o/cri-oAvatar de cri-o

    cri-o/cri-o

    5,629Voir sur GitHub↗

    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.

    Go
    Voir sur GitHub↗5,629
  • opencontainers/runtime-specAvatar de opencontainers

    opencontainers/runtime-spec

    3,641Voir sur GitHub↗

    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.

    Gocontainersdockeroci
    Voir sur GitHub↗3,641
  • nestybox/sysboxAvatar de nestybox

    nestybox/sysbox

    3,458Voir sur GitHub↗

    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.

    Shellcontainer-runtime-securitycontainer-runtimescontainers
    Voir sur GitHub↗3,458
  1. Home
  2. Software Engineering & Architecture
  3. Dependency Injection Containers
  4. Container Runtime Hooks

Explorer les sous-tags

  • Lifecycle Hook Name EnumerationsLists and validates the recognized names of supported container lifecycle hooks. **Distinct from Container Runtime Hooks:** Distinct from Container Runtime Hooks: focuses specifically on enumerating recognized hook names in specifications rather than executing driver injections.
  • PostStop Hook Failure HandlingsTerminates a container properly even when its PostStop hook fails. **Distinct from Container Runtime Hooks:** Distinct from Container Runtime Hooks: focuses on handling failures of PostStop hooks specifically, not general pre-start hook injection.