Apple container vs Inclavare Containers
Apple container
github.comInclavare Containers
github.comSide by side
| Figure | Apple container | Inclavare Containers |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| macOS | Yes | — |
| Linux | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Container Engines | 8.0 (#8) | 7.6 (#13) |
| Purpose | Apple container creates and runs Linux containers as lightweight virtual machines on a Mac. | Inclavare Containers is a container runtime for launching protected containers in hardware-assisted Trusted Execution Environments (TEEs). |
Plans
In their own words
Apple container
Apple container creates and runs Linux containers as lightweight virtual machines on a Mac. Written in Swift and optimized for Apple silicon, it gives each container its own lightweight virtual machine with core utilities and libraries. Host data is shared by mounting only the data needed inside each virtual machine. The tool consumes and produces OCI-compatible images that can be pulled from and pushed to standard registries. Documented features include CPU and memory limits, bind mounts, named volumes, tmpfs, DNS-based names, port forwarding, and isolated networks. It can run local single-node or multi-node Kubernetes clusters for development and testing, and documentation covers building, running, and publishing images for Apple silicon and x86-64. Integrations include macOS Virtualization, vmnet, XPC, launchd, Keychain services, and unified logging. Apple container is free, Apache-2.0 licensed, and supported on macOS 26, but requires Apple silicon. The project is under active development.
Inclavare Containers
Inclavare Containers is a free, open-source Linux container runtime for launching protected containers in hardware-assisted Trusted Execution Environments. It creates hardware-enforced isolation between a tenant workload and privileged cloud-provider software. Its Enclave Attestation Architecture provides remote attestation that sensitive workloads run on trusted TEE hardware. The rune component is described as compliant with the OCI Runtime specification, while documented integrations include dockerd, containerd, and pouchd. Deployment can use Occlum LibOS or WebAssembly Micro Runtime, and Rats-TLS provides an attested secured channel between heterogeneous TEEs. shim-rune handles enclave signing and management between containerd and rune; epm manages cache pools for enclave startup. The project is cloud-platform agnostic and can run on public-cloud Kubernetes platforms. It supports Kubernetes CRI, uses the OCI image format, and documents Linux hosts including Ubuntu 18.04 and Alibaba Linux 2. Installation is described through source builds or RPM/DEB repositories.