convert-to-apple-container

To switch to the Apple Container runtime, the migration updates the CLI binary from Docker to Apple Container, converts mount syntax, updates build scripts, and runs integration tests to verify the native runtime works correctly.

Yes, migrating to Apple Container preserves Dockerfile compatibility so existing build definitions continue to work while the runtime, CLI binary, and mount syntax are updated for macOS native isolation.

The best way to handle mount syntax changes is converting existing Docker volume syntax to Apple Container's native mount format while preserving mount security validation during the runtime migration process.

Yes, the migration automatically runs integration checks to verify the Apple Container runtime is functioning, auto-starts the runtime if it is stopped, and cleans up any orphaned containers left from previous Docker usage.

Updating startup checks and orphan detection is required because the migration switches the underlying runtime binary, necessitating new verification logic to ensure the Apple Container runtime is active and old Docker containers are safely removed.

You should use Apple Container instead of Docker when you need macOS-native OS-level isolation for local NanoClaw development or deployment and want a deterministic, test-verified migration path away from standard Docker runtime.