diff --git a/sites/docs-devsy-sh/content/docs/managing-providers/microsandbox.mdx b/sites/docs-devsy-sh/content/docs/managing-providers/microsandbox.mdx index fc1e2639f..476184be2 100644 --- a/sites/docs-devsy-sh/content/docs/managing-providers/microsandbox.mdx +++ b/sites/docs-devsy-sh/content/docs/managing-providers/microsandbox.mdx @@ -50,10 +50,16 @@ Set options in Desktop or with `devsy provider set microsandbox -o KEY=value`. I | `MICROSANDBOX_WORKSPACE_STAT_VIRTUALIZATION` | `strict` | Use `strict`, `relaxed`, or `off`. `off` requires `private` permissions. | | `INACTIVITY_TIMEOUT` | Empty | Stop after a duration such as `10m` or `1h`. | +`MSB_PATH` and `MSB_LIBKRUNFW_PATH` are provider options. The provider does not read them from the environment of the shell that runs Devsy, so exporting them has no effect. When they are empty, the provider uses the first `msb` it finds on `PATH`, then `~/.local/bin/msb`, then `~/.microsandbox/bin/msb`. + ## Diagnostics and limits If the runtime version cannot be recognized, update it with `msb self update`. If inspect output cannot be parsed, the provider reports the runtime version and an incompatibility reporting link. For a relocated runtime, set both executable and firmware paths. A partial pair fails instead of selecting another installation. The installed adapter's `runtime-check` command checks the pair and version without starting a VM, although it can initialize the native library cache. +An invalid option value, such as `MICROSANDBOX_MEMORY=abc`, stops the provider before it starts. In provider release v1.0.4, Devsy then shows only `Unrecognized remote plugin message` and `runtime supervisor failed`. Run the command again with `--debug` to see the cause, for example `invalid MICROSANDBOX_MEMORY`. A later provider release reports the option error in the normal output. + +`msb` rejects a bind mount host path that goes through a symbolic link, such as `/tmp` on macOS. In provider release v1.0.4, starting a workspace from a folder under `/tmp`, or with a `DEVSY_HOME` under `/tmp`, fails with `bind mount host path ... goes through symlink /tmp`. Use the resolved path, for example `/private/tmp/project`. A later provider release resolves these paths itself. + The external runtime driver does not support Compose devcontainers. Use a Docker driver provider when your workspace requires Compose. For a relocated runtime, `runtime-check` reads its process environment rather than saved provider options. Pass the same paths configured with `devsy provider set` to the installed adapter. For example, in a shell: