compute:service
compute:service
Section titled “compute:service”Install, inspect, drain and uninstall the Connected Compute runner OS service
Options:
| Flag | Description | Required |
|---|---|---|
--service-user <name> | Unprivileged user the system-scope unit runs as | No |
--system | Use system scope (systemd system unit); requires root and —service-user | No |
--service-name <name> | Service name | No |
--runner-dir <path> | Runner directory (default: ~/.lumenflow) | No |
--dry-run | Print the unit and environment-file plan without writing or running anything | No |
--read-write-path <path> | System scope: an extra path the sandboxed unit may write (for example the workspace root); repeatable | No |
--register-session | Register the session with the control plane (needs the token env var). OPT-IN: the control plane can resolve registration and claim to different session keys, so an unsolicited registration may shadow the runtime-owned session and make every claim fail | No |
--operator-approved | Operator attestation that the runner capabilities and posture are approved in the workspace (admission is operator-led); nothing verifies it automatically | No |
--session-token-env <name> | Environment variable holding the workspace API token; its value is stored in the environment file and never accepted on the command line | No |
--capabilities <csv> | Comma-separated capability set the service advertises | No |
--session-id <id> | Runner session id (default: runner-<hostname>) | No |