docs(website): sync dev docs from d97709fb5b

This commit is contained in:
github-actions[bot]
2026-10-20 13:31:13 +00:00
parent 5ec68b89f1
commit 8a44d0dafc
2 changed files with 9 additions and 3 deletions
+3 -3
View File
@@ -1,8 +1,8 @@
snapshots:
dev:
source-ref: 7417f75384a02a12b30b736cc185bb08b814bd40
source-sha: 7417f75384a02a12b30b736cc185bb08b814bd40
version: 0.1.5.dev77
source-ref: d97709fb5b3756413edd924137562e3339787014
source-sha: d97709fb5b3756413edd924137562e3339787014
version: 0.1.5.dev81
latest:
source-ref: 5a7728c304b5528e954e9ae900cf21f84e1a12b1
source-sha: 5a7728c304b5528e954e9ae900cf21f84e1a12b1
@@ -238,6 +238,12 @@ VM sandboxes have no network interface. All traffic flows through the OpenShell
If the gateway is briefly unavailable while a VM starts, its supervisor retries the session connection. The sandbox stays in provisioning until the gateway accepts the session.
### MicroVM Stop Durability
When you run `openshell sandbox stop` while the main process is running, OpenShell terminates the workload and flushes the guest root filesystem before acknowledging termination. The guest waits up to three seconds for the flush. The host allows up to 22 seconds for supervisor shutdown, then up to five seconds to stop the VM.
Flush errors and timeouts produce warnings while shutdown continues. If a signal kills the supervisor, the driver warns that the guest flush was not confirmed and recent writes may be lost. A completed stop does not guarantee persistence after a failed or timed-out flush. This flush does not cover stops after the main process has already exited.
### MicroVM Mounts
The VM driver shares gateway-host directories into the guest with virtiofs. Each entry in `mounts` takes `source` (absolute host directory), `target`, optional `read_only` (default `true`), and optional `type`, which must be `bind` so Docker and Podman bind entries work unchanged: