Skip to content
Back to search

apple-container

MarketplaceWorks with Claude CodeGitHub

Skills for using container, Apple's tool for running Linux containers on macOS

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/apple/container with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/apple/container'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/apple-container/badge.svg)](/listings/apple-container)

HTML

<a href="/listings/apple-container"><img src="/api/listings/apple-container/badge.svg" alt="findsafeskills safety rating" /></a>

Install

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 15 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "apple-container",
  3. "description": "Skills for using container, Apple's tool for running Linux containers on macOS",
  4. "owner": {
  5. "name": "The container project maintainers"
  6. },
  7. "plugins": [
  8. {
  9. "name": "container",
  10. "description": "Teaches Claude container's command surface and how it maps to Docker, Lima, Colima, and Podman on macOS",
  11. "version": "0.1.0",
  12. "source": "./"
  13. }
  14. ]
  15. }
README.md · README · 110 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <h1>
  2. <img alt="Containerization logo" src="./assets/Containerization-Logo.png" width="70" valign="middle">
  3. &nbsp;container
  4. </h1>
  5. `container` is a tool that you can use to create and run Linux containers as lightweight virtual machines on your Mac. It's written in Swift, and optimized for Apple silicon.
  6. The tool consumes and produces [OCI-compatible container images](https://github.com/opencontainers/image-spec), so you can pull and run images from any standard container registry. You can push images that you build to those registries as well, and run the images in any other OCI-compatible application.
  7. `container` uses the [Containerization](https://github.com/apple/containerization) Swift package for low-level container, image, and process management.
  8. <img src="./docs/assets/landing-movie.gif" width="830" alt="Introductory movie: running a web server in a container, then opening an Ubuntu container machine that shares your home directory">
  9. ## Get started
  10. ### Requirements
  11. You need a Mac with Apple silicon to run `container`. To build it, see the [BUILDING](./BUILDING.md) document.
  12. `container` is designed to run on macOS 26 or later, since it takes advantage of new features and enhancements to virtualization and networking in this release. We do not support older versions of macOS and the `container` maintainers typically will not address issues that cannot be reproduced on macOS 26 or later.
  13. ### Initial install
  14. Download the latest signed installer package for `container` from the [GitHub release page](https://github.com/apple/container/releases).
  15. To install the tool, double-click the package file and follow the instructions. Enter your administrator password when prompted, to give the installer permission to place the installed files under `/usr/local`.
  16. Start the system service with:
  17. ```bash
  18. container system start
  19. ```
  20. ### Run your first container
  21. ```bash
  22. container run --rm alpine echo hello
  23. ```
  24. This pulls the `alpine` image, runs it in a lightweight Linux VM, prints `hello`, and
  25. removes the container when it exits. See the [tutorial](./docs/tutorials/start-here.md)
  26. for a fuller walkthrough that builds and publishes an image of your own.
  27. ### Upgrade or downgrade
  28. For both upgrading and downgrading, you can manually download and install the signed installer package by following the steps from [initial install](#initial-install) or use the `update-container.sh` script (installed to `/usr/local/bin`).
  29. If you're upgrading or downgrading, you must stop your existing `container`:
  30. ```bash
  31. container system stop
  32. ```
  33. To upgrade to the latest release, simply run the command below:
  34. ```bash
  35. /usr/local/bin/update-container.sh
  36. ```
  37. To downgrade, you must uninstall your existing `container` (the `-k` flag keeps your user data, while `-d` removes it):
  38. ```bash
  39. /usr/local/bin/uninstall-container.sh -k
  40. /usr/local/bin/update-container.sh -v 0.3.0
  41. ```
  42. Start the system service with:
  43. ```bash
  44. container system start
  45. ```
  46. ### Uninstall
  47. Use the `uninstall-container.sh` script (installed to `/usr/local/bin`) to remove `container` from your system. To remove your user data along with the tool, run:
  48. ```bash
  49. /usr/local/bin/uninstall-container.sh -d
  50. ```
  51. To retain your user data so that it is available should you reinstall later, run:
  52. ```bash
  53. /usr/local/bin/uninstall-container.sh -k
  54. ```
  55. ## Next steps
  56. - Take [a guided tour of `container`](./docs/tutorials/start-here.md) by building, running, and publishing a simple web server image.
  57. - Learn how to [use various `container` features](./docs/how-to.md).
  58. - Explore the [container-examples repo](https://github.com/apple/container-examples/) that contains examples that show you how to work with `container`, such as [developing Linux apps in a container machine with Visual Studio Code](https://github.com/apple/container-examples/tree/main/container-machine-vscode) and [running a three-tier app on a container cluster behind a gateway](https://github.com/apple/container-examples/tree/main/container-cluster-gateway).
  59. - Read a brief description and [technical overview](./docs/technical-overview.md) of `container`.
  60. - Browse the [full command reference](./docs/command-reference.md).
  61. - [Build and run](./BUILDING.md) `container` on your own development system.
  62. - View the project [API documentation](https://apple.github.io/container/documentation/).
  63. ## Contributing
  64. Contributions to `container` are welcome and encouraged. Please see our [main contributing guide](https://github.com/apple/containerization/blob/main/CONTRIBUTING.md) for more information.
  65. ## Project Status
  66. The container project is under active development. Its release versions are product versions, not semantic versions.
  67. The `container` CLI compatibility generally preserves backward compatibility within a major release (not breaking existing scripts), however, there may be the odd case where breaking compatibility may be necessary. **Note:** Features marked *experimental* (for example, the `cluster` subcommand) may change and do not guarantee backward compatibility.
  68. The `container-apiserver` XPC API compatibility preserves forward and backward compatibility within a major version.
  69. Other non-public XPC helpers do not guarantee CLI or API compatibility across different versions.
  70. The `container` application data provides forward compatibility only, guaranteed within one major version. Upgrading to a newer major version may require a specific upgrade path.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.