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
·

14 dépôts

Awesome GitHub RepositoriesNetwork Namespace Virtualization

Creation of isolated TCP/IP stacks using kernel network namespaces.

Distinct from Network Virtualization Tools: Specifically implements a full isolated network stack via namespaces rather than general network virtualization tools

Explore 14 awesome GitHub repositories matching devops & infrastructure · Network Namespace Virtualization. Refine with filters or upvote what's useful.

Awesome Network Namespace Virtualization 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.
  • collabnix/dockerlabsAvatar de collabnix

    collabnix/dockerlabs

    8,008Voir sur GitHub↗

    dockerlabs is a collection of educational labs and technical tutorials designed to teach the fundamentals of containerization and microservice architecture. It provides instructional material and hands-on exercises covering image optimization, security training, infrastructure setup, and cluster orchestration. The project features specific courses and guides focused on reducing image size through multi-stage builds, securing workloads via vulnerability scanning and encrypted networks, and deploying multi-node clusters with high availability using Swarm orchestration. The materials cover a br

    Covers attaching containers to specific network drivers to manage service communication and isolation.

    PHPadvancebeginnersdocker
    Voir sur GitHub↗8,008
  • netblue30/firejailAvatar de netblue30

    netblue30/firejail

    7,069Voir sur GitHub↗

    Firejail is a Linux application sandbox and kernel security wrapper that isolates untrusted applications from the host system. It uses kernel namespaces and seccomp filters to restrict filesystem access, drop kernel capabilities, and limit the system attack surface. The project is distinguished by its use of predefined security profiles to automatically apply filesystem restrictions and syscall limits based on the executable being launched. It provides specialized isolation for portable packages such as AppImages and implements X11 display isolation via proxy servers to prevent keyboard loggi

    Initializes a separate TCP/IP stack with its own routing table and firewall for traffic isolation.

    C
    Voir sur GitHub↗7,069
  • weaveworks/weaveAvatar de weaveworks

    weaveworks/weave

    6,614Voir sur GitHub↗

    Weave is a multi-host container networking tool that connects containers running on different physical machines into a single virtual network. It creates a software-defined overlay network spanning multiple hosts, enabling containers to communicate directly with each other as if they were on the same local switch. The system provides automatic service discovery, resolving container names to network addresses across hosts without manual configuration. Traffic between containers on different hosts is secured through encrypted tunnels, preventing eavesdropping and tampering. Weave also includes

    Attaches containers to a virtual Ethernet bridge for direct L2 connectivity across hosts.

    Go
    Voir sur GitHub↗6,614
  • superradcompany/microsandboxAvatar de superradcompany

    superradcompany/microsandbox

    6,570Voir sur GitHub↗

    Microsandbox is a runtime for creating and managing lightweight, hardware-isolated virtual machines — called sandboxes — that boot directly from standard OCI container images. Each sandbox runs as its own host process with a separate kernel, filesystem, and network stack, providing process-per-sandbox isolation. The project includes a command-line tool and multi-language SDKs (Rust, TypeScript, Python, Go) for programmatic lifecycle control, and it communicates with sandbox agents over Unix sockets using a CBOR-encoded protocol. What distinguishes Microsandbox is its combination of host-manag

    Deletes sandboxes and their persisted state, with optional force-stop before removal.

    Rust
    Voir sur GitHub↗6,570
  • containernetworking/cniAvatar de containernetworking

    containernetworking/cni

    6,050Voir sur GitHub↗

    Attaches network interfaces into container network namespaces by executing plugins.

    Gocontainersdockerkubernetes
    Voir sur GitHub↗6,050
  • mininet/mininetAvatar de mininet

    mininet/mininet

    5,817Voir sur GitHub↗

    Mininet is a network emulator that creates virtual networks of hosts, switches, and links on a single Linux machine for Software-Defined Networking (SDN) prototyping and testing. It emulates network nodes as lightweight processes in isolated network namespaces, connecting them via virtual Ethernet pairs, and supports OpenFlow protocol for programmable control of virtual switches and traffic flows. The project enables users to design custom network topologies using a Python API, simulate link conditions such as bandwidth, delay, and packet loss, and run real Linux applications and kernel code

    Emulates entire network nodes as lightweight processes in isolated namespaces, the core architecture of the emulator.

    Python
    Voir sur GitHub↗5,817
  • containers/bubblewrapAvatar de containers

    containers/bubblewrap

    5,839Voir sur GitHub↗

    Bubblewrap is a Linux sandbox runner that creates lightweight, isolated execution environments for running untrusted applications. It combines Linux user, mount, network, PID, and UTS namespaces with seccomp-BPF system call filtering to restrict filesystem, network, process, and inter-process communication access. The project provides comprehensive process isolation by giving each sandbox its own private tmpfs root with selective bind-mounts, a separate network stack containing only a loopback interface, an independent process ID space, and remapped user and group identifiers. It applies secc

    Gives the sandbox its own network namespace with only a loopback interface, blocking external access.

    Clinux-containersuser-namespaces
    Voir sur GitHub↗5,839
  • 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

    Removes network namespace entries such as veth pairs when a sandbox is removed.

    Go
    Voir sur GitHub↗5,629
  • lxc/lxdAvatar de lxc

    lxc/lxd

    5,554Voir sur GitHub↗

    LXD is a unified platform for managing both system containers and virtual machines through a single REST API and command-line interface. It provides a programmatic HTTP interface for controlling the full lifecycle of instances, enabling automation and integration with external tools. The system runs unprivileged containers with per-instance UID/GID mappings, seccomp filters, and AppArmor profiles for kernel-level isolation, while supporting multiple storage backends including directory, Btrfs, LVM, ZFS, Ceph, LINSTOR, and TrueNAS through a unified driver interface. The platform distinguishes

    Adds a virtual network interface to an instance or profile, connecting it to a managed or external network.

    Go
    Voir sur GitHub↗5,554
  • lxc/incusAvatar de lxc

    lxc/incus

    4,893Voir sur GitHub↗

    Incus is a unified orchestration platform for managing system containers, OCI application containers, and virtual machines through a single control plane. It brings together cluster infrastructure management, secure multi-tenancy, software-defined networking, and pluggable storage backend orchestration into one cohesive system exposed via a full REST API and command-line interface. What distinguishes Incus is its ability to run multiple instance types side by side—full Linux system containers, OCI application containers, and QEMU virtual machines—all managed with consistent tooling. Networkin

    Connects an instance to a network using multiple attachment modes including bridging, MACVLAN, SR-IOV, OVN, physical pass-through, IPVLAN, point-to-point, and routed modes.

    Gocloudcontainershacktoberfest
    Voir sur GitHub↗4,893
  • testcontainers/testcontainers-dotnetAvatar de testcontainers

    testcontainers/testcontainers-dotnet

    4,317Voir sur GitHub↗

    Testcontainers for .NET est une bibliothèque de test Docker et un framework de test d'intégration conçu pour gérer le cycle de vie de conteneurs éphémères. Il fournit des abstractions de haut niveau en tant que wrapper de l'API Docker pour provisionner une infrastructure éphémère, remplaçant les mocks par de vraies instances de base de données, de messagerie et de moteur de recherche pour garantir des environnements de test isolés et reproductibles. Le projet se distingue par un modèle de configuration de conteneur par builder et un mécanisme de liaison de port dynamique qui évite les collisions lors de l'exécution de tests concurrents. Il permet une communication service-à-service fiable via l'orchestration de réseau virtuel et l'aliasing réseau, et assure la disponibilité des services via des vérifications de disponibilité basées sur le polling pour les endpoints HTTP et les ports TCP. La bibliothèque fournit des modules spécialisés pour les bases de données relationnelles, NoSQL et vectorielles, ainsi que des courtiers de messagerie et des émulateurs de services cloud. Sa surface de capacité s'étend à la configuration d'images de conteneur, à la collecte de logs et à la simulation de conditions réseau pour vérifier la résilience du système. Elle prend en charge la connectivité aux runtimes Docker locaux et distants via des variables d'environnement et des fichiers de configuration standardisés.

    Allows attaching existing containers to virtual networks to enable communication between disparate resources.

    C#automationdockerdotnet
    Voir sur GitHub↗4,317
  • jpetazzo/pipeworkAvatar de jpetazzo

    jpetazzo/pipework

    4,251Voir sur GitHub↗

    Pipework est une boîte à outils de mise en réseau définie par logiciel et un utilitaire de gestion conçu pour automatiser les configurations réseau pour les conteneurs Linux. Il fournit des outils pour gérer les adresses IP, créer des topologies réseau virtuelles et intégrer des conteneurs dans diverses architectures réseau. Le projet se distingue par un support spécialisé pour la configuration des périphériques InfiniBand IPoIB, incluant la gestion des clés de partition. Il propose également une intégration avec Open vSwitch pour l'automatisation des ponts et l'isolation VLAN, ainsi que la capacité de lier des conteneurs directement au matériel hôte physique via des sous-interfaces macvlan. Ses capacités plus larges couvrent une gestion réseau complète, incluant l'assignation IP statique et DHCP, la manipulation des règles de routage et la configuration de la passerelle par défaut. Il inclut également des utilitaires pour surveiller la disponibilité des interfaces et simuler des conditions réseau telles que la latence et la perte de paquets au sein des espaces de noms des conteneurs.

    Executes network configuration commands directly within isolated Linux network namespaces to ensure container traffic separation.

    Shell
    Voir sur GitHub↗4,251
  • 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

    Transfers physical or virtual network devices into container network namespaces for connectivity.

    Gocontainersdockeroci
    Voir sur GitHub↗3,641
  • rootless-containers/rootlesskitAvatar de rootless-containers

    rootless-containers/rootlesskit

    1,273Voir sur GitHub↗

    RootlessKit is a tool for running container workloads and isolated process trees securely as a standard non-privileged user without holding root access on the host. It creates unprivileged user and mount namespaces to simulate fake root execution environments, allowing users to execute container workloads and manage resource groups safely. The project provides capabilities for rootless port forwarding and unprivileged network namespace isolation, routing container network traffic through user-mode packet translation without requiring privileged kernel setup. It includes multiple backend netwo

    Creates isolated TCP/IP stacks using kernel network namespaces.

    Gorootless-containers
    Voir sur GitHub↗1,273
  1. Home
  2. DevOps & Infrastructure
  3. Infrastructure
  4. Networking
  5. Routing
  6. Network Virtualization Tools
  7. Network Namespace Virtualization

Explorer les sous-tags

  • Cleanups on Sandbox Removal2 sous-tagsRemoves network namespace entries such as veth pairs when a sandbox is removed rather than when it is stopped. **Distinct from Network Namespace Virtualization:** Distinct from Network Namespace Virtualization: focuses on cleanup timing (on sandbox remove vs stop), not on creating isolated stacks.
  • Container Network Attachments4 sous-tagsAttaching network interfaces directly into a container's network namespace via plugin execution. **Distinct from Network Namespace Virtualization:** Distinct from Network Namespace Virtualization: focuses on attaching interfaces to container namespaces, not creating isolated TCP/IP stacks.
  • Loopback-Only Network IsolationGives the sandbox its own network namespace with only a loopback device, cutting off all external network connectivity. **Distinct from Network Namespace Virtualization:** Distinct from Network Namespace Virtualization: focuses on providing only a loopback device for network isolation, not general network namespace creation.
  • Loopback-Only Network NamespacesGives the sandbox its own network namespace with only a loopback interface, cutting off external access. **Distinct from Network Namespace Virtualization:** Distinct from Network Namespace Virtualization: focuses on providing only a loopback interface, not general network namespace creation.
  • Loopback-Only Network StacksCreates a separate network stack with only a loopback interface, cutting all external network connectivity. **Distinct from Network Namespace Virtualization:** Distinct from Network Namespace Virtualization: focuses on providing only a loopback interface, cutting off all external connectivity, rather than general network namespace creation.
  • Network Namespace DetachmentsIsolates network namespaces into dedicated state directories while executing commands in the host context. **Distinct from Network Namespace Virtualization:** Distinct from general network namespace virtualization: specifically isolates namespaces into state directories while executing child commands in the host context.
  • Process-Based Network Node EmulationsEmulates network nodes as lightweight Linux processes in isolated network namespaces instead of full virtual machines. **Distinct from Network Namespace Virtualization:** Distinct from Network Namespace Virtualization: focuses on running full network node processes (hosts, switches) in namespaces, not just creating isolated TCP/IP stacks.