This article explains how Alibaba's open‑source PouchContainer adds both unit‑test and integration‑test coverage reporting using Go's cover tool, TravisCI, Codecov, and custom test harnesses, providing step‑by‑step commands, code snippets, and PR details to raise overall coverage from 18% to 60%.
Alibaba’s PouchContainer, an internally built container runtime, combines LXC and Docker technologies to enable full‑scale, non‑intrusive containerization of online services, offering rich features such as systemd‑based rich containers, enhanced isolation, P2P image distribution, in‑place upgrades, and native Kubernetes integration.
This article chronicles Alibaba's eight‑year journey from monolithic applications to a fully containerized, image‑based infrastructure, detailing the evolution of PouchContainer, its technical architecture, large‑scale deployment, Docker compatibility, and the operational practices that enabled seamless migration across the group.
Alibaba achieved full internal containerization by evolving from monolithic apps to the T4 container, integrating Docker images, and open‑sourcing PouchContainer, detailing the architectural shifts, resource isolation requirements, large‑scale deployment strategies, and lessons for building cloud‑native platforms.
PouchContainer, Alibaba's open‑source rich‑container engine, delivers strong isolation, high portability, and low resource usage, enabling enterprises to rapidly containerize legacy workloads while preserving existing operations and unlocking cloud‑native benefits at massive scale.
This article explains how PouchContainer implements container networking using the CNM model and libnetwork, detailing sandbox, endpoint, and network concepts, built‑in network modes, and the step‑by‑step flow of the Connect API with code examples.
PouchContainer introduces an upgrade API that allows seamless, in‑place upgrades of stateful containers by preserving network, storage, and configuration while reducing API calls, offering consistency, flexibility, and robustness for enterprise‑scale deployments.
This article explains PouchContainer's volume architecture, the supported volume types—including local, tmpfs, and Ceph—how to create and manage them with CLI commands, compares volumes with bind mounts, and outlines future CSI integration for container storage.
This article explains the motivation behind the Kubernetes Container Runtime Interface (CRI), outlines its design, and provides a detailed walkthrough of PouchContainer’s CRI manager architecture, including pod creation, network configuration, and I/O stream handling, with code examples and configuration snippets.
PouchContainer 0.5.0 introduces lightweight, open‑source container enhancements such as CRI v1alpha2 support, dynamic env updates, improved image engine, storage plugins, network management, and extensive stability fixes, aiming to boost large‑scale data‑center resource utilization and simplify legacy workload containerization.
Alibaba’s nine‑year Double‑11 evolution grew transaction volume 280‑fold, prompting a unified scheduling system (Sigma), mixed‑deployment of online and offline tasks via Sigma and Fuxi, and a cloud‑native architecture that leverages PouchContainer, resource isolation, and dynamic scaling to cut IT costs and boost resource utilization.
Starting from version 0.3.0, PouchContainer integrates the open‑source LXCFS FUSE filesystem to isolate /proc views inside containers, allowing existing monitoring and deployment tools to read container‑specific metrics without modification, and the article details the use cases, command‑line integration, and stability improvements.
