Version 1.4.1 gives every container its own VM
Apple container takes a different route from the usual Mac container stack. Version 1.4.1 starts a lightweight Linux virtual machine for each container instead of putting every workload inside one shared guest. Host folders are mounted only into the VM that needs them, giving each container a VM isolation boundary. Apple still consumes and produces OCI images, so an image built here can move to another standards-compatible runtime.
That design suits a Mac developer who wants stronger boundaries between local workloads without managing a general-purpose Linux VM first. The CLI pulls and pushes images, builds Dockerfiles, and manages volumes and networks. Its services use macOS facilities including Virtualization, vmnet, XPC, and launchd. Those choices explain the tight integration and narrow host support.
What happened when we ran it
commit eafe6b8 stopped before execution in our lab. The checkout was Swift, the repository had no Dockerfile, and our test host was an unprivileged Debian container with 3 CPUs and 8 GB of RAM. Apple requires an Apple-silicon Mac for the runtime, with macOS 26 as the supported release. There is no install time, build result, test count, or benchmark to report from that environment.
A supported-host trial is still necessary. Our Debian finding answers one purchasing question: evaluation cannot move into a generic Linux CI job. It says nothing about startup speed, image-build speed, or runtime overhead on a Mac, and we will not substitute Apple's description for our own measurement. Test the actual images, mounts, registry, and network setup on the Mac hardware your team will use.
The signed installer is short, while DNS takes three steps
On macOS 26, download the signed package, approve installation under /usr/local, then run container system start. A first alpine command pulls the image, runs it in a Linux VM, and removes the container. Upgrades require stopping the system service. Downgrades add an uninstall step, with separate flags for keeping or deleting user data.
Local name resolution is fussier. The tutorial requires a domain in ~/.config/container/config.toml, a service restart, and a privileged command that writes under /etc/resolver. Open issue 1693 had 34 comments and was updated on September 22, 2026; its reporter described intermittent host lookups on macOS 26.5. That report does not cover every setup, but DNS deserves a check before moving a multi-service project.
OCI images travel, but Docker workflows need edits
Version 1.4.1 covers daily single-container operations well. It builds Dockerfiles, talks to standard registries, supports bind mounts and named volumes, and has user-defined networks on macOS 26. Rosetta can help run x86_64 workloads. Container machines provide a persistent Linux environment, while an experimental Kubernetes command can create a local cluster and load images into it.
The command line is familiar without being a Docker clone. Apple's Claude Code skill warns that command groups are singular and tells agents to consult help rather than infer a subcommand. Docker Compose has no equivalent. Commands including restart, commit, attach, top, rename, and pause are absent, as is Docker's restart policy. Existing scripts need an audit before anyone swaps the executable name.
VM isolation can hold on to freed guest memory
One VM per container gives Apple a clean isolation story, but macOS 26 has a resource caveat. The technical overview says the Virtualization framework provides only partial memory ballooning. A guest may free pages for Linux while macOS continues to count them as occupied. Apple advises occasionally restarting containers when many memory-intensive workloads keep host memory use high. That matters on laptops where databases and build workers stay open all day.
Release 1.4.1 shipped on September 9, 2026 and fixed 2 security issues in the underlying Containerization package. One involved symlinks escaping expected OCI extraction paths; the other involved a Unix socket path-length mismatch. The release also added a clean command. Apple says product versions are not semantic versions and experimental commands can break compatibility.
September 2026 activity is high, with rough edges still visible
GitHub showed 50,160 stars, 542 open issues and pull requests, and a last push on September 25, 2026. That combined open count is not a bug count. Recent work included a fix for the Kubernetes plugin's iptables backend and documentation for self-contained tests. Release 1.4.1 arrived during the same month as the commit our lab inspected.
Issue 2299 reports terminal rendering corruption with tmux, Vim, and other full-screen programs under container exec -it on version 1.4.1. Issue 1194 records a certificate failure inside an emulated x86_64 AlmaLinux 10 container. Neither report establishes a universal failure. They are useful acceptance tests for teams that depend on interactive terminal tools or Intel Linux images.
Choose it for a macOS 26 workflow you can keep Mac-specific
Apple container makes the most sense when the host is already fixed: Apple silicon, macOS 26, Dockerfiles, and individual OCI containers. The VM boundary is a meaningful reason to try it, and the registry format keeps the images useful elsewhere. The included Claude Code skill is candid about missing commands, which should reduce plausible but wrong Docker translations.
Keep the incumbent stack when local development depends on Compose, identical commands across Mac and Linux, or mature lifecycle controls. Podman offers a wider host story, Lima exposes the Linux VM directly, and Multipass is clearer for a full Ubuntu environment. The macOS 26 requirement and absent Compose path should decide whether Apple container belongs on your team's schedule.