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

Entdecke die besten Open-Source-Repositories mit KI-gestützter Suche.

EntdeckenKuratierte SuchenOpen-Source-AlternativenSelf-hosted SoftwareBlogSitemap
ProjektMCP-ServerÜber unsRanking-MethodikPresse
RechtlichesDatenschutzAGB
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·

14 Repos

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

Finde die besten Repos mit KI.Wir suchen mit KI nach den am besten passenden Repositories.
  • collabnix/dockerlabsAvatar von collabnix

    collabnix/dockerlabs

    8,008Auf GitHub ansehen↗

    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
    Auf GitHub ansehen↗8,008
  • netblue30/firejailAvatar von netblue30

    netblue30/firejail

    7,069Auf GitHub ansehen↗

    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
    Auf GitHub ansehen↗7,069
  • weaveworks/weaveAvatar von weaveworks

    weaveworks/weave

    6,614Auf GitHub ansehen↗

    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
    Auf GitHub ansehen↗6,614
  • superradcompany/microsandboxAvatar von superradcompany

    superradcompany/microsandbox

    6,570Auf GitHub ansehen↗

    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
    Auf GitHub ansehen↗6,570
  • containernetworking/cniAvatar von containernetworking

    containernetworking/cni

    6,050Auf GitHub ansehen↗

    Attaches network interfaces into container network namespaces by executing plugins.

    Gocontainersdockerkubernetes
    Auf GitHub ansehen↗6,050
  • mininet/mininetAvatar von mininet

    mininet/mininet

    5,817Auf GitHub ansehen↗

    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
    Auf GitHub ansehen↗5,817
  • containers/bubblewrapAvatar von containers

    containers/bubblewrap

    5,839Auf GitHub ansehen↗

    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
    Auf GitHub ansehen↗5,839
  • cri-o/cri-oAvatar von cri-o

    cri-o/cri-o

    5,629Auf GitHub ansehen↗

    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
    Auf GitHub ansehen↗5,629
  • lxc/lxdAvatar von lxc

    lxc/lxd

    5,554Auf GitHub ansehen↗

    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
    Auf GitHub ansehen↗5,554
  • lxc/incusAvatar von lxc

    lxc/incus

    4,893Auf GitHub ansehen↗

    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
    Auf GitHub ansehen↗4,893
  • testcontainers/testcontainers-dotnetAvatar von testcontainers

    testcontainers/testcontainers-dotnet

    4,317Auf GitHub ansehen↗

    Testcontainers for .NET ist eine Docker-Testbibliothek und ein Integrationstest-Framework, das für die Verwaltung des Lebenszyklus von kurzlebigen Containern entwickelt wurde. Es bietet High-Level-Abstraktionen als Docker-API-Wrapper zur Bereitstellung ephemerer Infrastruktur und ersetzt Mocks durch echte Datenbank-, Messaging- und Suchmaschineninstanzen, um isolierte und reproduzierbare Testumgebungen zu gewährleisten. Das Projekt zeichnet sich durch ein Builder-Konfigurations-Container-Muster und einen dynamischen Port-Binding-Mechanismus aus, der Kollisionen während der gleichzeitigen Testausführung verhindert. Es ermöglicht zuverlässige Service-zu-Service-Kommunikation via virtueller Netzwerk-Orchestrierung und Netzwerk-Aliasing und stellt die Serviceverfügbarkeit durch Polling-basierte Bereitschaftsprüfungen für HTTP-Endpunkte und TCP-Ports sicher. Die Bibliothek bietet spezialisierte Module für relationale, NoSQL- und Vektor-Datenbanken sowie Messaging-Broker und Cloud-Service-Emulatoren. Ihr Funktionsumfang erstreckt sich auf Container-Image-Konfiguration, Log-Sammlung und die Simulation von Netzwerkbedingungen zur Überprüfung der Systemresilienz. Sie unterstützt die Konnektivität zu lokalen und Remote-Docker-Runtimes durch standardisierte Umgebungsvariablen und Konfigurationsdateien.

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

    C#automationdockerdotnet
    Auf GitHub ansehen↗4,317
  • jpetazzo/pipeworkAvatar von jpetazzo

    jpetazzo/pipework

    4,251Auf GitHub ansehen↗

    Pipework is a software-defined networking toolkit and management utility designed to automate network configurations for Linux Containers. It provides tools for managing IP addresses, creating virtual network topologies, and integrating containers into various network architectures. The project distinguishes itself through specialized support for InfiniBand IPoIB device configuration, including the management of partition keys. It also features integration with Open vSwitch for bridge automation and VLAN isolation, as well as the ability to bind containers directly to physical host hardware v

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

    Shell
    Auf GitHub ansehen↗4,251
  • opencontainers/runtime-specAvatar von opencontainers

    opencontainers/runtime-spec

    3,641Auf GitHub ansehen↗

    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
    Auf GitHub ansehen↗3,641
  • rootless-containers/rootlesskitAvatar von rootless-containers

    rootless-containers/rootlesskit

    1,273Auf GitHub ansehen↗

    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
    Auf GitHub ansehen↗1,273
  1. Home
  2. DevOps & Infrastructure
  3. Infrastructure
  4. Networking
  5. Routing
  6. Network Virtualization Tools
  7. Network Namespace Virtualization

Unter-Tags erkunden

  • Cleanups on Sandbox Removal2 Sub-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 Sub-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.