awesome-repositories.com
博客
MCP
awesome-repositories.com

通过 AI 驱动的搜索,发现最优秀的开源仓库。

探索精选搜索开源替代品自托管软件博客网站地图
项目MCP 服务器关于排名机制媒体报道
法律隐私政策服务条款
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·

6 个仓库

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

用 AI 发现最棒的仓库。我们将通过 AI 为您搜索最匹配的仓库。
  • collabnix/dockerlabscollabnix 的头像

    collabnix/dockerlabs

    8,008在 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
    在 GitHub 上查看↗8,008
  • weaveworks/weaveweaveworks 的头像

    weaveworks/weave

    6,614在 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
    在 GitHub 上查看↗6,614
  • containernetworking/cnicontainernetworking 的头像

    containernetworking/cni

    6,050在 GitHub 上查看↗

    Attaches network interfaces into container network namespaces by executing plugins.

    Gocontainersdockerkubernetes
    在 GitHub 上查看↗6,050
  • lxc/lxdlxc 的头像

    lxc/lxd

    5,554在 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
    在 GitHub 上查看↗5,554
  • lxc/incuslxc 的头像

    lxc/incus

    4,893在 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
    在 GitHub 上查看↗4,893
  • testcontainers/testcontainers-dotnettestcontainers 的头像

    testcontainers/testcontainers-dotnet

    4,317在 GitHub 上查看↗

    Testcontainers for .NET 是一个 Docker 测试库和集成测试框架,旨在管理一次性容器的生命周期。它提供高级抽象作为 Docker API 包装器来配置临时基础设施,用真实的数据库、消息队列和搜索引擎实例替换 Mock,以确保隔离且可重现的测试环境。 该项目的特色在于构建器-配置-容器模式和动态端口绑定机制,可防止并发测试执行期间的冲突。它通过虚拟网络编排和网络别名实现可靠的服务间通信,并通过针对 HTTP 端点和 TCP 端口的基于轮询的就绪检查确保服务可用性。 该库为关系型、NoSQL 和向量数据库以及消息代理和云服务模拟器提供了专门的模块。其功能范围扩展到容器镜像配置、日志收集和网络状况模拟,以验证系统弹性。 它通过标准化的环境变量和配置文件支持连接到本地和远程 Docker 运行时。

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

    C#automationdockerdotnet
    在 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

探索子标签

  • 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 个子标签Connects 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.