back to microsandbox

compare

microsandboxvsapple container

pick apple container for apple-native linux container tooling on apple silicon. [1] pick microsandbox for an agent runtime that embeds across macos, linux, and windows preview.

apple container is a swift tool for creating and running linux containers as lightweight virtual machines on apple silicon. it consumes and produces oci-compatible images, and each workload gets a vm rather than an ordinary shared-kernel macos process. [1]

this comparison uses the verified 0.12.x release line, not an assumed 1.0 label. [2] its strongest fit is an apple-native local container workflow, including the cli and swift packages maintained in the public repository. [1]

microsandbox uses the same own-kernel principle for a different job. it is an embeddable runtime for agent and untrusted-code sandboxes, with native sdks and a deployment path beyond a single apple silicon mac.

microsandbox
local + cloud
apple container
vm-per-container tooling on apple silicon [1]
isolation
hardware-isolated microvm · its own kernel
lightweight virtual machine per linux container [1]
license
apache 2.0
apache 2.0 [1]
release examined
0.6.8 · pinned runtime for this site
0.12.x · not an assumed 1.0 release [2]
host platforms
macOS · Linux · Windows (WHP, preview)
macos on apple silicon [1]
image workflow
pull oci images through the sandbox runtime
pull, build, run, and push oci images [1]
programming model
embeddable agent runtime and cli
apple container cli and swift packages [1]
destination
local runtime · private beta. access is by request.
local container workflows on a supported mac [1]
pick apple container

choose apple container when

  • your target is an apple silicon mac. [1]
  • you want apple-native tooling to build and run oci containers. [1]
  • the swift packages or container cli are the interface you need. [1]
pick microsandbox

choose microsandbox when

  • the runtime also needs to work on linux or windows preview.
  • your application creates agent sandboxes through an sdk.
  • destination-bound credentials and host network policy are part of the boundary.
  • one sdk. one api. local or cloud is a config change, not a rewrite.

01

how to choose

choose apple container when the product is the mac-local container workflow itself. its cli and swift packages expose image and container operations directly, and its apple silicon requirement is a deliberate platform fit. [1]

choose microsandbox when the application needs to create an agent computer rather than operate a general container tool. the sdk owns sandbox lifecycle, policy, and the path from the local machine to another deployment target.

common questions

what is apple container?

apple container is an apache-2.0 swift tool for building and running linux containers in lightweight virtual machines on apple silicon macs. [1]

is microsandbox an apple container alternative?

for own-kernel local execution, the products overlap. apple container is general apple-native container tooling. microsandbox is an embeddable runtime for agent and untrusted-code sandboxes.

does apple container run each container in a vm?

yes. the project describes linux containers running as lightweight virtual machines on the mac. [1]

does apple container run on linux?

no. the project requires a mac with apple silicon. [1] microsandbox also runs on linux and offers windows whp support in preview.

can apple container use oci images?

yes. it consumes and produces oci-compatible images and works with standard registries. [1] microsandbox also uses oci images as its workload input.

run it locally.

put the boundary on your own machine before you choose anything else.

run it locally