Using docker-socket-proxy method doesn't get all ports and doesn't pull the names of containers

[ee-boi]

First of all - this is a great utility, really appreciate it!

I am trying to setup using the docker-socket-proxy method. When I do this it doesn't find all the ports on my server, and it just lists my docker containers as "docker-proxy" and does not list them as their actual name. When I switch away from the docker-proxy and use - /var/run/docker.sock:/var/run/docker.sock:ro instead it gets all ports (host machine and docker) and names everything correctly. Is this the intended behavior?

compose file for portracker:

services:
  portracker:
    image: mostafawahied/portracker:latest
    container_name: portracker
    restart: unless-stopped
    pid: "host"
    cap_add:
      - SYS_PTRACE
      - SYS_ADMIN
    security_opt:
      - apparmor:unconfined
    volumes:
      - ./portracker-data:/data
#      - /var/run/docker.sock:/var/run/docker.sock:ro
    ports:
      - "4999:4999"
    environment:
      - DOCKER_HOST=tcp://docker-proxy:2375

compose file for docker-socket-proxy:

services:
  dockerproxy:
    image: tecnativa/docker-socket-proxy:latest
    container_name: dockerproxy
    restart: unless-stopped
    expose:
      - "2375"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      AUTH: 0
      SECRETS: 0
      POST: 1 #When disabled, only GET and HEAD operations are allowed, meaning any section of the API is read-only.
      BUILD: 0
      COMMIT: 0
      CONFIGS: 0
      CONTAINERS: 1
      ALLOW_START: 1 #(containers/id/start)
      ALLOW_STOP: 1 #(containers/id/stop)
      ALLOW_RESTARTS: 1 #(containers/id/stop|restart|kill)
      DISTRIBUTION: 1
      EXEC: 1
      GRPC: 0
      IMAGES: 1
      INFO: 1
      NETWORKS: 1
      NODES: 0
      PLUGINS: 0
      SERVICES: 1
      SESSION: 0
      SWARM: 0
      SYSTEM: 0
      TASKS: 1
      VOLUMES: 1
      PING: 1

[mostafa-wahied]

This seems to me like it might be an outdated image. Could you please redeploy making sure you are pulling the latest image, and report. You could remove the container and deploy with pulling latest.

[ee-boi]

Hi appreciate your reply, I haven't forgotten about this just got caught up lately with other things. Will test this out this week and report back.

[Konraddo]

I have the same issue. The containers, obtained via docker-proxy, are shown under docker-proxy:

Also, all their names are docker-proxy:

v.1.3.0

services:
  docker-proxy:
    image: tecnativa/docker-socket-proxy:latest
    container_name: portracker-docker-proxy
    environment:
      - CONTAINERS=1
      - IMAGES=1
      - INFO=1
      - NETWORKS=1
      - POST=0
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    ports:
      - "2375:2375"
    restart: unless-stopped

  portracker:
    image: mostafawahied/portracker:latest
    container_name: portracker
    pid: "host"
    cap_add:
      - SYS_PTRACE
      - SYS_ADMIN
    security_opt:
      - apparmor:unconfined
    environment:
      - DOCKER_HOST=tcp://docker-proxy:2375
    volumes:
      - portracker_data:/data
    ports:
      - "4999:4999"
    network_mode: bridge
    depends_on:
      - docker-proxy
    restart: unless-stopped

volumes:
  portracker_data:
    external: true

[eleventhaus]

weird its working fine for me. wonder if it has anything to do with caddy?

  docker-proxy:
    container_name: docker-proxy
    image: tecnativa/docker-socket-proxy:latest
    restart: unless-stopped
    ports:
      - "2375:2375"
    security_opt:
      - no-new-privileges=true
    environment:
      - CONTAINERS=1
      - IMAGES=1
      - INFO=1
      - NETWORKS=1
      - POST=0
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    networks:
      - portracker
      - uptime-kuma
    healthcheck:
      test: wget --spider http://localhost:2375/version || exit 1
      interval: "60s"
      timeout: "15s"
      retries: 3
      start_period: "15s"

  portracker:
    container_name: portracker
    image: mostafawahied/portracker:latest
    restart: unless-stopped
    depends_on:
      - docker-proxy
    pid: "host" # Required for port detection
    # Required permissions for system ports service namespace access
    cap_add:
      - SYS_PTRACE # Linux hosts: read other PIDs' /proc entries
      - SYS_ADMIN # Docker Desktop: allow namespace access for host ports (required for MacOS)
    security_opt:
      - apparmor:unconfined # Required for system ports
    ports:
      - "4999:4999"
    volumes:
      # Required for data persistence
      - /Users/server/Docker/appdata/portracker:/data
    environment:
      - ENABLE_AUTH={$ENABLE_AUTH}
      - SESSION_SECRET={$SESSION_SECRET}
      - DOCKER_HOST=tcp://docker-proxy:2375
    # Optional: For enhanced TrueNAS features
    # - TRUENAS_API_KEY=your-api-key-here
    networks:
      - proxy
      - portracker

[mostafa-wahied]

Thanks @eleventhaus.

Yea I can reproduce the issue by using wrong DOCKER_HOST name or wrong container name

Try matching your compose to this:

services:
  docker-proxy:
    image: tecnativa/docker-socket-proxy:latest
    restart: unless-stopped
    environment:
      - CONTAINERS=1
      - IMAGES=1
      - INFO=1
      - NETWORKS=1
      - POST=0
      - PING=1
      - VERSION=1
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    expose:
      - "2375"

  portracker:
    image: mostafawahied/portracker:latest
    restart: unless-stopped
    pid: "host"
    cap_add:
      - SYS_PTRACE
      - SYS_ADMIN
    security_opt:
      - apparmor:unconfined
    volumes:
      - ./portracker-data:/data
    ports:
      - "4999:4999"
    environment:
      - DOCKER_HOST=tcp://docker-proxy:2375
    depends_on:
      - docker-proxy