convert-to-apple-container

To switch from Docker to Apple Container for macOS isolation, the skill replaces Docker in your runtime code and scripts, handling mount behavior, entrypoints, and verification across pre-flight and subsequent phases.

Apple Container is a macOS-native container runtime that provides native isolation. You need it when running projects like NanoClaw on macOS that require a deterministic transition from Docker with minimal disruption to existing interfaces.

Yes, you can switch the runtime to Apple Container with NanoClaw on macOS while minimizing disruption to existing interfaces. The skill updates runtime binaries, startup checks, and mount behavior while retaining the core project structure.

Yes, switching to Apple Container involves updating credential proxy binding and security. The skill's workflow includes a dedicated phase for credential proxy binding to ensure a safe and auditable runtime transition.

To verify a container runtime migration from Docker to Apple Container, a staged workflow runs pre-flight checks, applies code changes, and executes phase 2, 3, and 4 verification steps to ensure the transition is successful.

A limitation of replacing Docker with Apple Container is that it targets macOS environments specifically and requires updating mount and entrypoint behavior, which may not apply to projects not running on macOS or using NanoClaw.