Skip to content

Commit 2f96925

Browse files
committed
docs: confirm --user root + docker socket mount works on a standard dockerd install
User-confirmed on a real ovos-vm running standard dockerd: mounting the socket + --user root gets log bridging and Services: detection working from inside the containerized tui-client. Updated the README from 'might work, worth trying' to 'confirmed working' for that case, keeping the honest caveat that this specific combination was NOT sufficient under this project's own rootless-Podman test setup.
1 parent 56daf1b commit 2f96925

1 file changed

Lines changed: 17 additions & 10 deletions

File tree

README.md

Lines changed: 17 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -170,16 +170,23 @@ is a real, deliberate security tradeoff - it hands this container
170170
effective control over the host's whole Docker daemon - so it's
171171
opt-in, not a default.
172172

173-
If mounted, the container's own non-root user often won't have
174-
permission to use the socket as-is (confirmed: a plain UID match
175-
alone isn't enough under rootless Podman specifically - your exact
176-
fix may vary by host setup). `--user root` on `docker run` is the
177-
usual quick fix for a standard `dockerd` install where the socket is
178-
`root:docker`-owned; matching the host's `docker` group GID is the
179-
more targeted alternative if running as root isn't appealing. Exact
180-
behavior depends on your host's specific Docker/Podman setup enough
181-
that it's worth just trying it and adjusting rather than treating any
182-
one fix here as guaranteed.
173+
If mounted, the container's own non-root user won't have permission to
174+
use the socket as-is. `--user root` on `docker run` fixes this on a
175+
standard `dockerd` install (confirmed working) - matching the group
176+
GID owning the socket instead is the more targeted alternative if
177+
running as root isn't appealing:
178+
179+
```bash
180+
docker run -it --rm --network host \
181+
-v /var/run/docker.sock:/var/run/docker.sock \
182+
--user root \
183+
ghcr.io/andlo/ovos-tui-client:latest
184+
```
185+
186+
Confirmed NOT sufficient on its own under rootless Podman specifically
187+
(even `--user root` didn't help there in testing) - if you're on
188+
Podman rather than a standard root-owned `dockerd` socket, this may
189+
need more digging into your specific setup.
183190

184191
Images are tagged by version (`:0.1.17`) and `:latest`, built and
185192
published automatically on every release.

0 commit comments

Comments
 (0)