joakimp/pi-devbox
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: correct the "pi-studio has no bind flag" claim everywhere it was baked
Lint / hadolint (push) Successful in 10s
Details
Lint / skill-floor (push) Successful in 14s
Details
Lint / doc-drift (push) Failing after 18s
Details
Lint / actionlint (push) Successful in 31s
Details

Browse Source 
1e4c238 fixed README; the same claim lived in three more places, all wrong
since pi-studio 0.9.60 added /studio --listen-all:

- rootfs/usr/local/bin/studio-expose header (and so its --help; the sed range
  grows 2,31p -> 2,35p so --help still ends at "runs it backgrounded.")
- pi-devbox-environment skill section 7: --listen-all as a third path, plus the
  0.10 whole-URL / 409 / "link looks damaged" notes, the published-port rule,
  --stop before --port, and the on-host curl 403-vs-empty-reply diagnostic
- Dockerfile.variant STUDIO_PORT comment

Bridge and --listen-all on one port: whichever starts second fails, measured
both ways on tor-ms22 (v1.11.2): Studio "listen EADDRINUSE ... 0.0.0.0:8765"
with the bridge up; studio-expose rc 1 on socat "bind(...): Address already in
use" with a 0.0.0.0 listener up. README's warning now says both directions.

Cost: studio-expose and the skill are in rootfs/, which base_tag hashes, so the
next release rebuilds the base (recomputed with the CI recipe: base-6f3b20266de1
at 1e4c238 -> base-26d425cea6c2 now). Noted in the CHANGELOG Unreleased entry.
No pin changes. lint-shell, dockerfile-directives and base-hash guards pass;
check-doc-drift is red only for the unrelated pi-extensions 750b2a8 -> 0d8e417.
This commit is contained in:
Joakim Persson
2026-10-14 19:27:42 +02:00
parent 1e4c238a83
commit a8f5b35d2a
5 changed files with 56 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5 -4
View File
@@ -261,10 +261,11 @@ publish. Keep the publish on `127.0.0.1:` as in B: anyone who can reach the
port and has the full URL controls Studio, including running prompts and
reading or writing files, and there is no TLS.
> **Use B or C on a port, not both.** With `STUDIO_EXPOSE=1` the bridge holds
> the container's egress IP on `$STUDIO_PORT` from boot, and `--listen-all` on
> that same port fails with `EADDRINUSE` (`0.0.0.0` includes that address).
> If the bridge is running, start Studio *without* `--listen-all`.
> **Use B or C on a port, not both.** Whichever starts second fails with
> `EADDRINUSE`: `0.0.0.0` includes the egress IP the bridge binds. With
> `STUDIO_EXPOSE=1` the bridge holds `$STUDIO_PORT` from boot, so
> `/studio --listen-all --port 8765` fails. If the bridge is running, start
> Studio *without* `--listen-all`.
### Remote host (SSH / mosh)