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
@@ -189,7 +194,7 @@ Commit this file to share project defaults with your team.
189
194
190
195
VibePod starts a `vibepod-proxy` container alongside every agent. It acts as an HTTP(S) MITM proxy and logs all outbound requests to a SQLite database viewable in the Datasette UI (`vp logs start`).
191
196
192
-
The proxy is reachable inside the Docker network as `http://vibepod-proxy:8080`. It is not published on a host port.
197
+
VibePod injects the proxy endpoint into agent containers automatically over the internal runtime network. It is not published on a host port.
Copy file name to clipboardExpand all lines: docs/podman.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,6 +66,8 @@ VibePod uses the standard [Docker SDK for Python](https://docker-py.readthedocs.
66
66
67
67
The rootless Podman socket is discovered via `$XDG_RUNTIME_DIR/podman/podman.sock` (falling back to `/run/user/<uid>/podman/podman.sock`). The rootful socket at `/run/podman/podman.sock` is only used when running as root.
68
68
69
+
VibePod allows up to 10 seconds for runtime detection probes. If your Podman socket is slower on a particular host, set `VP_RUNTIME_PROBE_TIMEOUT` to a larger value in seconds before running `vp`.
70
+
69
71
## Known limitations
70
72
71
73
### Interactive attach
@@ -77,6 +79,26 @@ vp run claude -d
77
79
podman attach vibepod-claude-<id>
78
80
```
79
81
82
+
### User namespace mapping
83
+
84
+
If you want Podman to preserve your host UID/GID for compatible containers, set a user namespace mode such as `keep-id`:
85
+
86
+
```bash
87
+
vp run claude --runtime podman --userns keep-id
88
+
```
89
+
90
+
You can also set it globally:
91
+
92
+
```bash
93
+
export VP_CONTAINER_USERNS_MODE=keep-id
94
+
```
95
+
96
+
```yaml
97
+
container_userns_mode: keep-id
98
+
```
99
+
100
+
This works best for images that run as your host UID. Images that switch to a different in-container user may still produce remapped ownership on bind mounts.
101
+
80
102
### Volume permissions
81
103
82
104
Rootless Podman uses user-namespace remapping: your host UID is mapped to root inside the container, while other UIDs are mapped to subordinate ranges. Container images that drop privileges via `su` or `gosu` may encounter permission errors on bind-mounted files.
0 commit comments