You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `--from` flag accepts a Dockerfile path, a directory containing a Dockerfile, a full image reference (e.g. `myregistry.com/img:tag`), or a community sandbox name (e.g. `openclaw`).
Copy file name to clipboardExpand all lines: architecture/sandbox-connect.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -153,6 +153,8 @@ The `sandbox exec` path is identical to interactive connect except:
153
153
- The command string is passed as the final SSH argument
154
154
- The sandbox daemon routes it through `exec_request()` instead of `shell_request()`, spawning `/bin/bash -lc <command>`
155
155
156
+
When `openshell sandbox create` launches a `--no-keep` command or shell, it keeps the CLI process alive instead of `exec()`-ing into SSH so it can delete the sandbox after SSH exits. The default create flow, along with `--forward`, keeps the sandbox running.
157
+
156
158
### Port Forwarding (`forward start`)
157
159
158
160
`openshell forward start <port> <name>` opens a local SSH tunnel so connections to `127.0.0.1:<port>`
0 commit comments