convert-to-apple-container

To switch the macOS container runtime from Docker to Apple Container, this skill updates configuration files, build scripts, and runner logic to accommodate the new syntax. It then verifies the transition using integration tests for mount validation.

Yes, NanoClaw works with Apple Container on macOS by transitioning its backend runtime. The switch adjusts mount syntax, startup checks, and build scripts to ensure compatibility with Apple's native containerization.

The best way to transition Docker containers to Apple's native runtime is by automating configuration updates and verifying the switch. This skill modifies build scripts and validates read-write and readonly mounts through integration testing.

The container runtime switch handles mount syntax differences by automatically updating configuration files and container runner logic. This ensures existing mount setups work correctly under Apple Container's operational requirements.

Readonly and read-write mounts are validated after switching to Apple Container through a series of integration tests. These tests verify the updated container runner logic and mount syntax function correctly in the new environment.

Docker is the runtime being replaced, so you transition away from it. The switch targets macOS users wanting native isolation, updating existing NanoClaw configurations to leverage Apple Container instead of relying on Docker.