Compatibility
Current development environment
Section titled “Current development environment”| Area | Current boundary |
|---|---|
| Hardware | Apple silicon only; the v0.0.2 qualification target is one physical M4 Mac and one macOS VM. |
| macOS | macOS 26 or later. |
| Source toolchain | Swift tools 6.2; the exact compiler is recorded for qualification evidence. |
Apple container |
Versions 1.0.0 and 1.1.0 have provider conformance coverage for their declared capabilities. |
| Containerization | Version 0.35.0 is pinned behind the out-of-process helper; only its declared local capability subset is supported. |
| Manifest | Strict Manifest v3; CPU and memory requests and limits are required. Unsupported fields fail closed. |
| Control API | Version 2.2, authenticated over the local daemon socket. |
| State | SQLite schema v24 for standalone, node-local state. |
| Image platform | Linux ARM64 images on Apple silicon. |
These are development implementation boundaries. They do not establish a GA support claim. Phase 15 must repeat the declared provider/version lanes against the accepted source and signed artifacts before the final compatibility matrix is published.
Release boundaries
Section titled “Release boundaries”- Hostwright supports one Mac per installation. Multi-Mac operation is outside the v0.0.2 scope.
- The stack importer accepts a reviewed Compose subset. It does not provide a Docker API, Docker client compatibility, or full Compose behavior.
- Kubernetes, CRI, and Podman compatibility are outside the release scope.
- The desktop app’s signed packaging, accessibility, and VM lifecycle remain qualification items.
- Run
hostwright capabilities --jsonto see the exact capabilities of a specific build. Capability output does not replace current-source release evidence.
See Limitations and the core compatibility matrix for the source of truth.