# Orchard

A native Swift macOS interface for Apple container, with container and image management, Compose projects, local Kubernetes, Linux machines and local AI tools.

> This is the Markdown version of the Orchard page on OpenNavo, with the same facts as the web page: <https://opennavo.com/apps/orchard>

- **Latest version**: `2.7.1`
- **Developer**: Andrew Waters
- **Homepage**: <https://github.com/andrew-waters/orchard>
- **Categories**: [Virtualization & Containers](https://opennavo.com/categories/virtualization)
- **Install**: `brew install --cask orchard`
- **30-day installs**: 315
- **Homebrew**: Available; updated by Homebrew
- **Download URL**: <https://github.com/andrew-waters/orchard/releases/download/v2.7.1/Orchard-2.7.1.dmg>
- **SHA-256**: `485efd65cd3740c618e7b1be5784fcad181802778de5285b7fa11751d11f1832`

SHA-256 only checks that the download is complete; it is not a security certification.

## Installation and removal contents

```json
[
  {
    "declaration": {
      "app": [
        "Orchard.app"
      ],
      "target": "/Applications/Orchard.app"
    },
    "phase": "install",
    "sources": [
      "Orchard.app"
    ],
    "target": "/Applications/Orchard.app",
    "type": "app"
  },
  {
    "declaration": {
      "zap": [
        {
          "trash": [
            "~/Library/Application Support/Orchard",
            "~/Library/Caches/container-compose.Orchard",
            "~/Library/Preferences/container-compose.Orchard.plist"
          ]
        }
      ]
    },
    "phase": "cleanup",
    "sources": [],
    "type": "zap"
  }
]
```

## About

Orchard is a native Swift macOS application for managing Apple's container runtime. It complements the `container` command-line tools with a desktop interface and communicates with the daemon through typed XPC APIs rather than repeatedly launching the CLI and parsing text output.

### Containers and development
Create, start, stop and inspect containers; pull and search images; and build images from Dockerfiles with streamed BuildKit logs. The app provides live CPU, memory, network and disk information, a multi-pane log viewer, network and DNS management, a menu-bar companion and a Cmd+K command palette. Build records and logs survive application restarts.

### Projects and machines
Compose projects are planned using the same open-source Swift package that powers the separate `container compose` plugin. Unsupported compose keys are disclosed before execution rather than silently ignored. Dependency ordering does not guarantee service readiness because the runtime lacks health reporting. Orchard also manages persistent Linux container machines and local Kubernetes clusters using Apple's k8s plugin. Workload deployment remains with tools such as kubectl; Orchard prepares the context and offers node inspection.

### Local AI
The AI Models panel can discover existing Ollama, LM Studio and MLX servers or supervise an MLX model server. Inference runs on the host Mac's GPU, not inside the container VM. Orchard computes a container-reachable model endpoint and can inject `OPENAI_BASE_URL` when creating a container. A Sandboxes view provides model-linked containers, isolation information, chat and terminal access and a stop control.

### Requirements and installation
The official 2.6.0 requirements list macOS 26 Tahoe and Apple container 1.6.0. The notes also state compatibility with container 1.5.x, with the new 1.6-only features unavailable. Install Apple container separately, then use `brew install --cask orchard` or the official DMG. Version 2.6.0 adds worker nodes, no-CNI clusters, committing containers to images and custom machine accounts with container 1.6.0+. Worker count and machine account are selected at creation. A read/write home mount allows processes inside the machine, including root via passwordless sudo, to modify Mac home files. Orchard is MIT-licensed and maintained by Andrew Waters.

### Sources
- [Official repository and README](https://github.com/andrew-waters/orchard)
- [Official 2.5.1 release and requirements](https://github.com/andrew-waters/orchard/releases/tag/v2.5.1)
- [Official documentation](https://orchard.andon.dev/)
- [Homebrew cask](https://github.com/Homebrew/homebrew-cask/blob/HEAD/Casks/o/orchard.rb)

## System requirements

- macOS 26 or later · Version: 2.7.1 · Intel · <https://github.com/homebrew/homebrew-cask/blob/HEAD/Casks/o/orchard.rb> · Checked 2026-11-22
  - <https://github.com/andrew-waters/orchard/releases/download/v2.7.1/Orchard-2.7.1.dmg>
  - SHA-256: `485efd65cd3740c618e7b1be5784fcad181802778de5285b7fa11751d11f1832`
- macOS 26 or later · Version: 2.7.1 · Apple silicon · <https://github.com/homebrew/homebrew-cask/blob/HEAD/Casks/o/orchard.rb> · Checked 2026-11-22
  - <https://github.com/andrew-waters/orchard/releases/download/v2.7.1/Orchard-2.7.1.dmg>
  - SHA-256: `485efd65cd3740c618e7b1be5784fcad181802778de5285b7fa11751d11f1832`

## Orchard security facts

Only facts that can be checked, each with its source and date. This is not a safety certification. To check the files you downloaded, scan them on your Mac with OpenNavo.

- <https://github.com/andrew-waters/orchard> · Open source: Yes — <https://github.com/andrew-waters/orchard> · Checked 2026-11-13

## Uninstall

- `brew uninstall --cask orchard`

A regular uninstall removes the app and keeps its settings and caches.

### Deep clean (optional)

- `brew uninstall --zap --cask orchard`

`--zap` also deletes the settings, caches and other files listed in the Homebrew definition. They can include data shared with other apps and cannot be restored, and it does not guarantee that nothing is left. Back up any data you need first. To keep settings and caches, leave out `--zap`.

A regular uninstall removes the app and keeps its settings and caches.

- Files and folders: `~/Library/Application Support/Orchard` — <https://github.com/homebrew/homebrew-cask/blob/HEAD/Casks/o/orchard.rb> · These entries come from the Homebrew definition, checked 2026-11-22. They say what it declares, not what is on your Mac.
- Files and folders: `~/Library/Caches/container-compose.Orchard` — <https://github.com/homebrew/homebrew-cask/blob/HEAD/Casks/o/orchard.rb> · These entries come from the Homebrew definition, checked 2026-11-22. They say what it declares, not what is on your Mac.
- Files and folders: `~/Library/Preferences/container-compose.Orchard.plist` — <https://github.com/homebrew/homebrew-cask/blob/HEAD/Casks/o/orchard.rb> · These entries come from the Homebrew definition, checked 2026-11-22. They say what it declares, not what is on your Mac.

## Latest release notes

### 2.7.1 (2026-11-09)

### Orchard v2.7.1

Thank you for using Orchard, and for the bug reports, ideas and pull requests that keep making it better. If it's useful to you, please consider [starring Orchard on GitHub](https://github.com/andrew-waters/orchard). It takes a second and helps other people find it.

#### Changes
##### Added
- On Apple container 1.7.1, Create Cluster has a **Use local images** option, on by default, which lets the nodes pull from the Mac's own image store (`container cluster create --shared-image-store`) ([#173](https://github.com/andrew-waters/orchard/issues/173)). An image built or pulled in Orchard then runs in the cluster without a registry or a copy. A cluster's detail says whether it can see the Mac's images; one that can't points to **Recreate**, since only a create can turn it on. Recreate keeps the choice.
- Containers Orchard creates follow the `[container.dns]` defaults in container's `config.toml` (nameservers, search domains, options and domain), as `container run` does from container 1.7.1 ([#173](https://github.com/andrew-waters/orchard/issues/173)). A field set in Orchard wins, then `[container.dns]`, then Orchard's chosen default domain, then container's `[dns].domain`. This covers the Run form, compose, sandboxes and model servers. Settings > General shows the defaults read-only next to the DNS Domain picker, and the Run form's empty domain choice names the domain it falls back to.

- On Apple container 1.7.1, Create Cluster can size the workers apart from the control plane ([#174](https://github.com/andrew-waters/orchard/issues/174)). With workers, the resource fields say they size the control plane, and **Size the workers** under Advanced sets the CPUs and memory each worker gets (`--workers count=<n>,cpus=<n>,memory=<size>`). Left off, a worker gets container's single-node defaults: a quarter of the Mac's CPUs and memory, at least 2 CPUs and 2 GB. Recreate reads the sizes off the live workers, keeps a cluster made in a terminal with workers of several sizes as it is, and otherwise uses the sizes the cluster was created with. Below 1.7 only a plain count is sent, as before.
- On Apple container 1.7.1, the Clusters tab reads what container stored for each cluster when it was created (`container cluster ls --format json`) ([#174](https://github.com/andrew-waters/orchard/issues/174)). The list and detail show the cluster's Kubernetes version, and the detail its creation date. Recreate takes the CNI and Kubernetes version from that record, so a cluster created outside Orchard recreates with its real settings, and falls back to what Orchard remembers for clusters made before 1.7. Those show a short note that `container cluster ls` doesn't list them; they can still be deleted. A cluster container has a record of but whose nodes are gone is listed with no nodes, so it can be recreated or deleted. If `cluster ls` fails, the tab works from the containers as before.
- Settings > System shows the kernel against the one the installed container version recommends ([#174](https://github.com/andrew-waters/orchard/issues/174)). When an older version's kernel is still installed it shows both and offers **Use Recommended Kernel**. A custom kernel is shown as custom and isn't flagged.
- Settings > System shows whether container's image snapshots and container file systems are backed up by Time Machine, and offers **Leave Out of Backups** when they are ([#174](https://github.com/andrew-waters/orchard/issues/174)). Both can be rebuilt by pulling the image or recreating the container, and container 1.7.1 leaves them out on new installs only. It sets the same exclusion as `tmutil addexclusion`, only when you choose it, and never touches named volumes. Nothing prompts for it, so putting the folders back in your backups is respected.

##### Changed
- Orchard now builds against Apple container 1.7.1 (containerization 0.54.0), up from 1.6.1 (containerization 0.53.0), and **Install container** installs 1.7.1 ([#173](https://github.com/andrew-waters/orchard/issues/173)).
- **Load Image** is gone on Apple container 1.7.1, which removed `container cluster load-image` ([#173](https://github.com/andrew-waters/orchard/issues/173)); **Use local images** replaces it. On 1.6.x it works as before.
- Orchard no longer stops, force stops or deletes a single cluster node, on any container version ([#173](https://github.com/andrew-waters/orchard/issues/173)). Acting on one node breaks the cluster's Kubernetes state, and container 1.7.1's CLI refuses it too. The detail header, context menus, multi-select cards, menu bar and Cmd+K leave those actions out for a node or turn them off with a note pointing to Clusters, and Stop All and the bulk stop and remove skip nodes and leave them out of their counts. Logs, terminals, stats and export still work on a node, and a cluster is still stopped or deleted from Clusters, including one made before container 1.6.1.
- Orchard now uses compose 0.9.0, and takes the rules for a failed `post_start` or `pre_stop` hook from it rather than keeping its own copy ([#130](https://github.com/andrew-waters/orchard/issues/130)): whether the run stops or carries on, what a failure reports and how much of a hook's output is kept. Hooks behave and read exactly as before. The Compose tab offers the matching 0.9.0 plugin update.
- The foot of the Compose tab shows the installed `container compose` version on its own, and links to its release on GitHub. A development build shows as the release it came after, marked (dev), and links to the commit it was built from.

##### Fixed
- Orchard no longer calls any `vmlinux-*` kernel the recommended one ([#174](https://github.com/andrew-waters/orchard/issues/174)). Someone still on the kernel container 1.6.1 installed was told they had the recommended kernel on 1.7.1.
- In full screen the list and detail headers (search, filters, sort and the add buttons) are no longer hidden behind the toolbar ([#167](https://github.com/andrew-waters/orchard/issues/167)). They sit just below it while the window is full screen, and the windowed layout is unchanged.
- Containers in a Compose project can reach each other by name ([#130](https://github.com/andrew-waters/orchard/issues/130)). Compose containers were created with a bare hostname, which container's DNS never matches, so a service could not find another as `<container>.<domain>`. They are now created under Orchard's default DNS domain (Settings > General > DNS Domain, else container's own default), as containers from the Run form are, with the same nameservers as before. The foot of the Compose tab shows it as **Default domain**, which opens Settings to change it, and says when `container compose` in a terminal would use another, since that reads only container's default from `config.toml`. Containers already running pick it up when they are next recreated.

##### Security
- Orchard now builds with swift-nio 2.105.0, swift-nio-extras 1.35.2 and swift-nio-http2 1.46.0, up from 2.97.1, 1.33.0 and 1.42.0, to pick up the SwiftNIO security fixes for unbounded HTTP/1 headers, a `ByteBuffer` overflow, CRLF injection in request URIs, a decompression ratio bypass and HTTP/2 request smuggling ([#170](https://github.com/andrew-waters/orchard/issues/170)). These libraries come in through Apple container and its dependencies; nothing Orchard calls changed.

#### Installation

**[Homebrew](https://formulae.brew.sh/cask/orchard)**
```
brew install orchard
```
Already installed with Homebrew? Update with:
```
brew upgrade orchard
```

**Download**
1. Download [Orchard-2.7.1.dmg](https://github.com/andrew-waters/orchard/releases/download/v2.7.1/Orchard-2.7.1.dmg)
2. Open it and drag Orchard.app to your Applications folder
3. Launch Orchard from Applications

Orchard also updates itself: when a new release is out, it offers the update in the app.

#### Checksums
- **SHA256**: [Orchard-2.7.1.dmg.sha256](https://github.com/andrew-waters/orchard/releases/download/v2.7.1/Orchard-2.7.1.dmg.sha256)

#### System Requirements
- macOS 26 (Tahoe)
- [Apple container](https://github.com/apple/container/releases/tag/1.7.1) 1.7.1

## Facts and sources

- <https://opennavo.com/apps/orchard>
- <https://opennavo.com/apps/orchard/versions>
- <https://github.com/homebrew/homebrew-cask/blob/HEAD/Casks/o/orchard.rb> · Checked 2026-11-22
- <https://formulae.brew.sh/cask/orchard>
- <https://github.com/andrew-waters/orchard> · Checked 2026-11-13
