Oxcart vs Apple container: the docker CLI you know, or Apple’s new one

What each one is

Apple’s container is an open-source Swift tool, released alongside macOS 26, “for creating and running Linux containers using lightweight virtual machines on a Mac.” It is built on Apple’s Containerization package, which “executes each Linux container inside of its own lightweight virtual machine.” It consumes and produces OCI-compatible images. Version 1.5.0 shipped on September 29, 2026.

Oxcart is a native Mac app with its own Docker-compatible engine. It ships the docker CLI 29.9.0, Docker Compose 5.6.0 and Buildx 0.38.0, sets up offline in seconds, and keeps the engine out of sight while it works. Everything you already script against Docker (the CLI, the Engine API, Compose files) points at Oxcart through the oxcart Docker context.

Apple facts from github.com/apple/container and github.com/apple/containerization, checked October 10, 2026. “Not mentioned” means the README does not say, not that the feature cannot exist.

Choose Oxcart when your tools already speak Docker

Most projects carry years of Docker: a compose.yaml, a Makefile full of docker commands, CI scripts, Testcontainers in the test suite, a .devcontainer folder. Oxcart runs all of it without edits. Its verified integration paths include the docker CLI, Compose with healthcheck dependencies, init: true and network_mode: service:, Buildx, the Engine API build endpoint used by docker-py and Testcontainers, and the Dev Containers CLI 0.89.0. You can mount the Docker socket into a container for Testcontainers, Portainer or Traefik.

It is also quick at the operations you repeat all day. On one Apple M5 Max, Oxcart 0.1.2 measured:

Oxcart 0.1.2 measured 2026-10-10 with its bundled docker 29.9 client; OrbStack 2.2.3 and Docker Desktop 4.94.0 measured earlier the same day, on the same Mac and harness, with docker 29.4. Apple’s container was not part of this benchmark. Full table: all comparisons.

Choose Apple’s container when you want Apple’s own tool

Apple’s container is a good fit if you want a free, open-source tool from Apple, are happy to learn its container commands, and value its model of one lightweight virtual machine per container. It is young (1.5.0) and moving quickly, so check its README for the features your project needs.

Using both

They can live on the same Mac. Images are the common ground: both work with OCI images, so you can build with Buildx in Oxcart, push to your registry, and pull with Apple’s tool, or the other way round. Oxcart only touches its own oxcart Docker context, and never replaces another app’s command-line tools without asking.

Beyond running containers

• For coding agents: Oxcart’s MCP server lets Claude Code, Codex, Cursor and other agents see, diagnose and manage containers, read-only by default. Its crash diagnosis is 159 tokens against 2,014 for docker inspect plus docker logs. See Docker for AI coding agents.
• On the network: published and outbound TCP crosses the link between your Mac and Oxcart’s engine in TLS 1.3, and outbound connections are opened by the Mac, so your VPN and firewall rules apply. See container networking on a Mac.
• In the window: Compose projects grouped with their health, ports grouped by repository and branch, and an inspector with logs, stats, a terminal and files.

Questions

What is Apple’s container tool?

An open-source command-line tool from Apple, “for creating and running Linux containers using lightweight virtual machines on a Mac.” It is written in Swift, uses OCI-compatible images, runs on Apple silicon with macOS 26, and is licensed Apache-2.0. Its companion Swift package, Containerization, runs each Linux container inside its own lightweight virtual machine.

Can I use docker and docker compose with Apple’s container?

Apple’s README (checked October 2026) documents its own container command, such as container run --rm alpine echo hello. It does not mention the docker CLI, the Docker Engine API or Compose. If your workflow is built on those, Oxcart runs them as they are: it ships docker 29.9, Compose 5.6 and Buildx 0.38, and its engine speaks Docker API 1.40 to 1.54.

Do Oxcart and Apple’s container both need macOS 26?

Yes. Both need a Mac with Apple silicon and macOS 26 or later. Neither supports Intel Macs or older macOS releases.

Is Apple’s container faster than Oxcart?

We have not benchmarked Apple’s container, and Apple’s Containerization README claims “sub-second start times” without published measurements. Oxcart measured 42 ms for docker run --rm on an Apple M5 Max, the fastest of the three Docker-compatible runtimes we tested.

Which one is free?

Apple’s container is free and open source (Apache-2.0). Oxcart is free for 60 days, then $20 per user per major version, not a subscription.

Can I keep using images I build with one in the other?

Yes. Apple’s container consumes and produces OCI-compatible images, and Oxcart pulls, builds, saves and loads standard images. Push to a registry from one and pull from the other.

Sources and method

• Apple container: https://github.com/apple/container (description, requirements, commands, license, release 1.5.0 of 2026-09-29); Containerization: https://github.com/apple/containerization. Checked 2026-10-10.
• Oxcart benchmarks: Apple M5 Max, 36 GiB, macOS 27.2; every product at 8 CPUs and 12 GiB, one at a time, each started fresh; medians of five samples after a warmup.
• Oxcart compatibility: tested on Oxcart, 2026-10-10.