Integrations

Docker and local proxy

Connect to the Docker engine on the same host without exposing the socket directly to NasDash.

Docker management is optional. Choose Portainer, Dockhand, an HTTP(S) Docker-compatible API, or a Unix socket. The local socket proxy is one option; Portainer and Dockhand do not require it. See Docker connections.

Minimal complete Compose

Before starting a fresh installation, prepare the data directory using installation and permissions. This is required for the bind mount below; an existing installation must keep its data and runtime identity.

services:
  nasdash:
    image: ghcr.io/lucas-lepajollec/nasdash:latest
    restart: unless-stopped
    ports:
      - "2504:2504"
    volumes:
      - ./data:/app/data
    pid: host
    extra_hosts:
      - "host.docker.internal:host-gateway"

  docker-proxy:
    profiles: ["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:ro

The default command starts NasDash alone. For the optional local proxy, run the command below, then choose Address in Settings → Integrations → Docker. Enter docker-proxy in the host field and 2375 in the port field; the resulting endpoint is http://docker-proxy:2375. Keep the profile enabled on recreates and preserve the existing data mount.

docker compose --profile docker-proxy up -d
docker compose logs nasdash
Host  docker-proxy
Port  2375

Do not publish 2375:2375 for this scenario. Docker DNS resolves docker-proxy only between services on the same Compose network.

Limit capabilities

VariableUseful effect for NasDashRecommendation
CONTAINERS=1list, details, logsrequired
IMAGES=1list imagesas needed
VOLUMES=1list volumesas needed
NETWORKS=1network informationas needed
INFO=1engine informationrecommended
POST=1start, stop, restartonly for operator admins
DELETE=1deletionsdisabled 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.