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
·

6 dépôts

Awesome GitHub RepositoriesContainer Network Attachments

Attaching 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.

Explore 6 awesome GitHub repositories matching devops & infrastructure · Container Network Attachments. Refine with filters or upvote what's useful.

Awesome Container Network Attachments 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
  • 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
  • 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
  • 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 a managed network to a container or virtual machine as a NIC device with a chosen interface name.

    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
  1. Home
  2. DevOps & Infrastructure
  3. Infrastructure
  4. Networking
  5. Routing
  6. Network Virtualization Tools
  7. Network Namespace Virtualization
  8. Container Network Attachments

Explorer les sous-tags

  • Bridge-Based AttachmentsAttaches containers to a virtual Ethernet bridge on each host for direct L2 connectivity within an overlay network. **Distinct from Container Network Attachments:** Distinct from Container Network Attachments: focuses on bridge-based L2 attachment for overlay networking, not general interface attachment via plugins.
  • Network Interface Attachment Modes3 sous-tagsConnects an instance to a network using bridging, MACVLAN, SR-IOV, OVN, physical pass-through, IPVLAN, point-to-point, or routed modes. **Distinct from Container Network Attachments:** Distinct from Container Network Attachments: covers multiple attachment modes (bridging, MACVLAN, SR-IOV, OVN, physical pass-through, IPVLAN, point-to-point, routed), not just container namespace attachment.
  • Point-to-Point NIC AttachmentsCreates a virtual device pair with one end in the instance and the other on the host for direct connectivity. **Distinct from Routed NIC Attachment to Virtual Machines:** Distinct from Routed NIC Attachment to Virtual Machines: creates a direct virtual pair, not using host network routing.
  • Routed NIC Attachment to Virtual MachinesAttaches a NIC that uses the host network's routing, requiring manual gateway configuration or cloud-init for VMs. **Distinct from Container Network Attachments:** Distinct from Container Network Attachments: attaches a routed NIC using host network routing, requiring manual gateway configuration or cloud-init for VMs.