Integrations
Docker and local proxy
Connect to the Docker engine on the same host without exposing the socket directly to NasDash.
The recommended Compose setup provides tecnativa/docker-socket-proxy. NasDash calls this proxy over the Docker network; no proxy port is published on the host.
Minimal complete Compose
services:
nasdash:
image: ghcr.io/lucas-lepajollec/nasdash:latest
restart: unless-stopped
ports:
- "2504:2504"
volumes:
- ./data:/app/data
pid: host
depends_on:
- docker-proxy
extra_hosts:
- "host.docker.internal:host-gateway"
docker-proxy:
image: tecnativa/docker-socket-proxy:v0.5.0
restart: unless-stopped
environment:
CONTAINERS: 1
IMAGES: 1
VOLUMES: 1
NETWORKS: 1
INFO: 1
POST: 1
DELETE: 0
volumes:
- /var/run/docker.sock:/var/run/docker.sock:roStart the Compose stack, read the generated first-start passwords with docker compose logs nasdash, then add the Docker host in NasDash with:
http://docker-proxy:2375Do not publish 2375:2375 for this scenario. Docker DNS resolves docker-proxy only between services on the same Compose network.
Limit capabilities
| Variable | Useful effect for NasDash | Recommendation |
|---|---|---|
CONTAINERS=1 | list, details, logs | required |
IMAGES=1 | list images | as needed |
VOLUMES=1 | list volumes | as needed |
NETWORKS=1 | network information | as needed |
INFO=1 | engine information | recommended |
POST=1 | start, stop, restart | only for operator admins |
DELETE=1 | deletions | disabled by default |
Verify
docker compose ps
docker compose logs --tail 100 docker-proxy
docker compose exec nasdash node -e "fetch('http://docker-proxy:2375/_ping').then(r=>r.text()).then(console.log)"The last command should display OK. If it fails, verify that both services share the same network and that the proxy is running.