Native backend (beta)
Reference map
The detailed material, by topic. Start with the overview and try it if you have not used the native backend yet.
Install and versions
- Install and Install the prerelease: the
hack-nextchannel, running both backends, upgrade and rollback. - Prerelease channel: versions, platforms and what a release contains.
Commands and configuration
- Native authored commands: exactly
what
up,restart,down,ps,logs,execandrundo on native. - Native config import: preview and adopt an existing project's configuration.
- Native settings files: the committed project file and the per-machine file that replace exported variables.
The full native reference
The native backend reference is one long page. These are its main sections:
| Topic | Section |
|---|---|
| Which projects stay on Compose | Compose projects that stay on the Compose backend |
| Runtime setup, upgrade and rollback | Manual candidate upgrade and rollback |
| How a Compose file is read | Explicit normalized public Compose input |
| Container permissions | Container capabilities and the security model |
| Pulling images | Registry image acquisition without Docker |
| Registry sign-in | Registry credentials |
| Sharing your source tree | Explicit writable development source |
| What each command supports | Frontend integration status |
| Intel-only images | amd64 emulation with Rosetta 2 |
| Local HTTPS | Optional native HTTPS frontend |
| After a crash | Explicit cleanup after a dead foreground owner |
How it works
- Architecture: backends shows the two backends side by side.
- Architecture: native backend internals explains ownership, startup and cleanup with state charts.
- Model coverage lists what the formal models check and what they do not.