1.0.2

New

• Build images from a Dockerfile - The Images section gains a Build Image… action: edit a Dockerfile in-app, give it a tag, and build a local image with live output.
• Create a container or machine from any image. The image detail view now has Run Container and Create Machine actions that open the create sheet prefilled with that image.

Fixed

• False "Base Environment Missing" on a working install.
• Fresh-install "Repair" deadlock.

Changed

• Start/Stop moved to the toolbar's leading edge in the machine and container detail views, with the Details/Terminal toggle centred and the remaining actions kept on the right. Stop is no longer next to "Open in Terminal," so reaching for a shell can't accidentally stop the machine or container.
• Dependency on the container package is now a pinned remote reference (apple/container, exact 1.0.0) instead of a local path that assumed a specific checkout layout.

1.0.1

New

• More one-click stack templates. Alongside WordPress + MariaDB, the New Stack menu now offers PostgreSQL, PostgreSQL + Adminer, Mailpit (local email testing), Gitea, code-server (VS Code in the browser), and Nginx + host folder (serve a folder from your Mac). Templates are now data-driven, so they share one create flow.
• Integrated terminal for containers. Container detail gains a Details/Terminal toggle that opens an interactive shell inside a running container (exec), in addition to the existing machine terminal.
• Guided setup & health checks. ContainerManager now:
  • offers to download and install the container tool (latest release) when it isn't present;
  • requires a minimum version (1.0.0) and prompts to update an older install instead of failing silently;
  • detects when the services are running but the base Linux environment (kernel / init filesystem) didn't finish downloading, and offers a one-click Repair.
• App identity. The app now presents as "Container Manager" and is categorized as a Utility.

Note

If you get prompts to repair that aren't getting resolved, drop to a terminal and run container system start && container machine create alpine:latest --name test to initialise a basic container machine. Once that is done the UI should be happy. Will be fixed in a future release.

Fixed

• Machine terminal working directory. The integrated machine terminal now opens in your shared macOS home (/Users/<you>), matching Terminal.app, instead of the machine's /home/<you>.
  • Note: There is an existing report for container about the home directory path. While your local $HOME is mapped in the container machine, $HOME in the machine will point to /home/<you> not the linked host home folder. apple/container#1678
• code-server stack start failure. The code-server template no longer crashes on first launch with a permission error writing its config volume; it now uses an image that handles volume ownership correctly.

Docs

• Added a Stacks guide and a note about the one-time Metal Toolchain component needed to build the app.

1.0

This is the first public release of ContainerManager