Installer socktainer avec Homebrew

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• socktainer

Historique du projet

The upstream README describes socktainer as both a CLI and daemon, still closely tied to the fast-moving Apple Container ecosystem. The project tracks partial Docker Engine API compatibility and documents Docker CLI and Docker Compose workflows rather than presenting itself as a full Docker replacement.

The project's release history began with a v0.0.1 prerelease in September 2025 and reached v1.0.0 in June 2026, according to its official GitHub releases. That places it in the first wave of package-manager tools adapting Apple's newer local-container stack for developers who already have Docker-oriented muscle memory.

Historique d'adoption

Adoption evidence is early but concrete: the README documents Homebrew installation, GitHub release binaries, and a former project tap that users can untap after moving to the Homebrew formula.

The README also says the Podman Desktop Apple Container extension uses socktainer to visualize Apple containers and images, giving the tool a role beyond its own command line.

Modes d'utilisation

Typical use is to start socktainer, switch Docker to the automatically created socktainer context, and then run familiar commands such as docker ps, docker images, docker run, and Docker Compose workflows against Apple's container backend.

The daemon listens by default on $HOME/.socktainer/container.sock, supports common lifecycle, image, log, stats, health, and event operations, and exposes macOS-specific choices such as Apple Container VM memory mapping and volume sync modes.

Pourquoi les passionnés de paquets s'y intéressent

socktainer matters to package-manager and CLI culture because it is a compatibility shim: a small package that lets a new platform-native runtime participate in the Docker-shaped tooling ecosystem.

For Homebrew users, it is a good example of why formulae often package adapters rather than only upstream engines. The interesting artifact is not just the Swift daemon, but the way it bridges Docker contexts, Unix sockets, Compose expectations, Apple Silicon constraints, and rapidly changing vendor APIs.

Chronologie

• 2025-09: v0.0.1 prerelease published on GitHub.
• 2025-09: v0.1.0 and v0.2.0 followed as early public releases.
• 2026-06: v1.0.0 published with Apple Container 1.0.0-related changes.

Related projects

• Apple Container: the macOS container backend socktainer wraps.
• Docker Engine API and Docker CLI: the compatibility surface socktainer exposes to users.
• Podman Desktop Apple Container extension: a desktop integration that the socktainer README says uses socktainer.
• Colima and other local macOS container runtimes: neighboring tools in the macOS container developer workflow.

Sources

• https://api.github.com/repos/socktainer/socktainer/releases
• https://github.com/socktainer/socktainer#readme
• source_facts.executables
• source_facts.package-manager