kyle/boxmaker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Brief P12: inferproxy is required

Browse Source 
Approved 2026-09-17. Evidence is in docs/decisions.md.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
kyle
2026-09-17 00:38:32 -07:00
co-authored by Claude Fable 5.1
parent a4ebdc11af
commit 0612d80aa2
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/design.md
+3 -3
View File
@@ -61,9 +61,9 @@ ordinary outbound networking can reach the whole tailnet and the internet as the
1. `loopd` runs with no network namespace interfaces except loopback (`--network=none`). Its only
I/O is three Unix sockets on a shared volume.
2. `inferproxy` is a forwarder of about 100 lines: one Unix socket in, one fixed upstream out. If
M0 shows `llama-server` can listen on a Unix socket and it runs on the same host, drop
`inferproxy` and mount that socket instead.
2. `inferproxy` is a forwarder of about 100 lines: one Unix socket in, one fixed upstream out. The
upstream is the shared router's TCP listener on the host. It is required: `loopd` has no
network, and the router stays on TCP for its other clients.
3. `gatewayd` has outbound network only. It opens no listening TCP port. v0 approvals use replies
or emoji reactions, which arrive over the Mattermost WebSocket, so no callback URL is needed.
4. Tool containers get no network unless the grant names hosts. Granted network access goes through