How openeuler-mirror/isulad works
Main System Type and Purpose
• Type: A C/C++‐based container engine with a daemon‐client architecture.
• Purpose: Manage container lifecycles and images either via a CLI (“isula”) or via the Kubernetes CRI (gRPC) interface; support multiple runtimes (lxc, runc, kata) and image formats (OCI, external rootfs).
Out Top-Level Components
• Clients (left)
– CLI client (“isula”) via Unix‐socket REST API
– Kubernetes kubelet via Unix‐socket gRPC CRI API
• Daemon (center)
– Entry Layer (transport)
– Service/API Layer
– Core Modules & Executor
– Low-level components
• External Services (right)
– Container runtimes (lxc, runc, kata)
– CNI plugins
– Image registries (OCI)
– Filesystem drivers (overlay2, devmapper)
Layers and Their Relationships
1. Clients → Entry Layer
– CLI → REST server
– kubelet → gRPC CRI server + gRPC runtime/image services
• Entry Layer subsystems (src/daemon/entry):
– REST services (rest_containers_service, rest_images_service, rest_metrics_service)
– gRPC services (grpc_containers_service, grpc_images_service, grpc_network_service, grpc_volumes_service)
– CRI adapters (CRI runtime/image/pod services, stream server, CNI plugin loader)
2. Entry Layer → Service/API Layer
• Service Container API (modules/service)
• Service Image API (modules/service)
• Service Network, Volume, Metrics, Events APIs
• These use common “api” definitions (src/api/services)
3. Service/API Layer → Core Modules
• Core Modules (src/daemon/modules):
– Container (state, GC, health‐check, restart, restore)
– Image (embedded sqlite, OCI store, external)
– Network (CNI operator, native, CRI)
– Volume (local driver)
– Device/CDI (registry, parser, behavior)
– Spec (namespace, mount, security, verify)
– Runtime (runtime engines lcr/isula, shim monitor)
– Sandbox (controller manager, sandboxer grpc client)
– Events (collector, sender)
– Plugin, Log, NRI adapters
4. Core Modules → Executor → Mailbox → Low-Level Subsystems
• Executor (src/daemon/executor) invokes callbacks in modules.
• Mailbox (src/daemon/mailbox) handles asynchronous messages.
• Low-Level Subsystems:
– cgroup v1/v2 management (src/daemon/common/cgroup)
– Filesystem graphdrivers overlay2, devmapper (modules/image/oci/storage)
– Network namespaces, Veth/CNI plugin execution (modules/network/cni_operator/libcni)
– OCI registry HTTP calls (utils/http)
– Crypto, tar, sha256, archive (utils)
– Process shim (isulad-shim in src/cmd)
5. Modules → External Runtimes & Services
• Container runtime engines:
– LXC via liblxc (default)
– runc via exec of runc binary
– kata via kata-runtime
• CNI plugins invoked by libcni
• Image registries (remote HTTP)
Architectural Patterns and Technologies
• Layered/Clean Architecture – clear separation: transport → API → core modules → low‐level
• Plugin/Adapter Pattern – dynamic CNI plugins, runtime engines, device modules (CDI), NRI
• Event‐Driven – mailbox and events collector/sender
• Build & Config – CMake build, JSON/YAML configuration, C headers for APIs
• Communication – Unix sockets, gRPC, HTTP REST