Container GUI 1.0.0
Container GUI 1.0.0
Container GUI brings a focused, native SwiftUI interface to Apple Container on macOS. It covers the everyday workflow for managing containers, images, and the Apple Container service without requiring routine command-line use.
Highlights
- Run, search, start, stop, inspect, and safely delete containers.
- Follow bounded container logs and view live CPU, memory, network, and block-I/O statistics.
- Browse, inspect, pull, run, and delete container images.
- Check Apple Container service health, start or stop the service, review disk usage, and inspect recent logs.
- Guided setup for a missing executable, an unsupported CLI version, or a stopped service.
- Sanitized support diagnostics that redact common secrets and credentials.
- A native macOS interface with searchable tables, inspectors, sheets, keyboard shortcuts, and the new Container GUI app icon.
Requirements
- An Apple-silicon Mac running macOS 26 or later.
- Apple Container CLI 0.12.0 or later and earlier than 2.0.0.
Installation
- Download
Container-GUI.dmgbelow. - Open the disk image.
- Drag Container GUI to the Applications shortcut.
- Open Container GUI from Applications.
Important
This release is ad-hoc signed and is not notarized by Apple. On first launch, macOS may say it cannot verify the developer and block the app. This is expected for this release.
Allowing the app on first launch
- Try to open Container GUI once so macOS records the blocked launch.
- Open System Settings → Privacy & Security.
- Scroll down to the Security section and click Open Anyway for Container GUI.
- Authenticate when prompted, then confirm Open.
The Open Anyway button is normally available for about an hour after the blocked launch attempt. You do not need to disable Gatekeeper globally.
SHA-256
2ec34ce005fae0b2403ffe62611351b44e036beb23998cc274c86bb2960ed113 Container-GUI.dmg
Known limitations
Version 1.0 does not yet manage networks, volumes, builds, registry authentication, interactive terminals, import/export, DNS or kernel settings, prune operations, or remote container hosts. Image deletion can fail while a container still depends on the image.