[ALERT] 119/204037 (1) : Starting frontend dockerfrontend: cannot create listening socket [:::2375]

[johntdyer]

I am running the latest image

ghcr.io/tecnativa/docker-socket-proxy       latest           d6414b470cf2   3 weeks ago     19.3MB

I have reviewed https://github.com/Tecnativa/docker-socket-proxy/issues/109 and adjusted my docker file as suggested but it doesnt seem to make any difference

dockerproxy:
    image: ghcr.io/tecnativa/docker-socket-proxy:latest
    container_name: dockerproxy
    restart: unless-stopped
    privileged: true  
    
    environment:
      - CONTAINERS=1 # Allow access to viewing containers
      - POST=0 # Disallow any POST operations (effectively read-only)
      - DISABLE_IPV6=true
    ports:
      - 2375:2375
    labels:
      com.centurylinklabs.watchtower.enable: true

    volumes:
       - /var/run/docker.sock:/var/run/docker.sock:ro # Mounted as read-only

docker logs dockerproxy

➜  shared-config docker logs dockerproxy
[WARNING] 119/203850 (1) : config : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING] 119/203850 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy docker-events started.
[NOTICE] 119/203850 (1) : haproxy version is 2.2.32-4081d5a
[ALERT] 119/203850 (1) : Starting frontend dockerfrontend: cannot create listening socket [:::2375]
[WARNING] 119/203850 (1) : config : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING] 119/203850 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy docker-events started.
[NOTICE] 119/203850 (1) : haproxy version is 2.2.32-4081d5a
[ALERT] 119/203850 (1) : Starting frontend dockerfrontend: cannot create listening socket [:::2375]
[WARNING] 119/203851 (1) : config : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING] 119/203851 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy docker-events started.
[NOTICE] 119/203851 (1) : haproxy version is 2.2.32-4081d5a
[ALERT] 119/203851 (1) : Starting frontend dockerfrontend: cannot create listening socket [:::2375]
[WARNING] 119/203852 (1) : config : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING] 119/203852 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy docker-events started.
[NOTICE] 119/203852 (1) : haproxy version is 2.2.32-4081d5a
[ALERT] 119/203852 (1) : Starting frontend dockerfrontend: cannot create listening socket [:::2375]
[WARNING] 119/203853 (1) : config : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING] 119/203853 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy docker-events started.
[NOTICE] 119/203853 (1) : haproxy version is 2.2.32-4081d5a
[ALERT] 119/203853 (1) : Starting frontend dockerfrontend: cannot create listening socket [:::2375]
[WARNING] 119/203855 (1) : config : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING] 119/203855 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy docker-events started.
[NOTICE] 119/203855 (1) : haproxy version is 2.2.32-4081d5a
[ALERT] 119/203855 (1) : Starting frontend dockerfrontend: cannot create listening socket [:::2375]
[WARNING] 119/203859 (1) : config : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING] 119/203859 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy docker-events started.
[NOTICE] 119/203859 (1) : haproxy version is 2.2.32-4081d5a
[ALERT] 119/203859 (1) : Starting frontend dockerfrontend: cannot create listening socket [:::2375]
[WARNING] 119/203906 (1) : config : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING] 119/203906 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy docker-events started.
[NOTICE] 119/203906 (1) : haproxy version is 2.2.32-4081d5a
[ALERT] 119/203906 (1) : Starting frontend dockerfrontend: cannot create listening socket [:::2375]
[WARNING] 119/203919 (1) : config : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING] 119/203919 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy docker-events started.
[NOTICE] 119/203919 (1) : haproxy version is 2.2.32-4081d5a
[ALERT] 119/203919 (1) : Starting frontend dockerfrontend: cannot create listening socket [:::2375]
[WARNING] 119/203945 (1) : config : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING] 119/203945 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy docker-events started.
[NOTICE] 119/203945 (1) : haproxy version is 2.2.32-4081d5a
[ALERT] 119/203945 (1) : Starting frontend dockerfrontend: cannot create listening socket [:::2375]
[WARNING] 119/204037 (1) : config : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING] 119/204037 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy docker-events started.
[NOTICE] 119/204037 (1) : haproxy version is 2.2.32-4081d5a
[ALERT] 119/204037 (1) : Starting frontend dockerfrontend: cannot create listening socket [:::2375]
[WARNING] 119/204137 (1) : config : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING] 119/204137 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy docker-events started.
[NOTICE] 119/204137 (1) : haproxy version is 2.2.32-4081d5a
[ALERT] 119/204137 (1) : Starting frontend dockerfrontend: cannot create listening socket [:::2375]
[WARNING] 119/204238 (1) : config : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING] 119/204238 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy docker-events started.
[NOTICE] 119/204238 (1) : haproxy version is 2.2.32-4081d5a
[ALERT] 119/204238 (1) : Starting frontend dockerfrontend: cannot create listening socket [:::2375]
➜  shared-config

➜  shared-config docker version
Client: Docker Engine - Community
 Version:           26.0.2
 API version:       1.45
 Go version:        go1.21.9
 Git commit:        3c863ff
 Built:             Thu Apr 18 16:27:49 2024
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          26.0.2
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.9
  Git commit:       7cef0d9
  Built:            Thu Apr 18 16:27:49 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.6.14
  GitCommit:        9ba4b250366a5ddde94bb7c9d1def331423aa323
 runc:
  Version:          1.1.3
  GitCommit:        v1.1.3-0-g6724737f
 docker-init:
  Version:          0.19.0

[edwardando]

I also have this issue on my IPv4-only machine

[kevdogg]

I also have this issue. Not sure if my machine is IPv4 only

[iambricegg]

@edwardando and @kevdogg In IPv4-only host, you need to disable IPv6 binding in the container via the environment variable DISABLE_IPV6=1

environment:
      - CONTAINERS=1 # Allow access to viewing containers
      - POST=0 # Disallow any POST operations (effectively read-only)
      - DISABLE_IPV6=1

[hhschu]

Having the same issue as OP. Using the latest image and set DISABLE_IPV6=1 but still getting:

[WARNING] 162/193047 (1) : config : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[WARNING] 162/193047 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory

tecnativa/docker-socket-proxy            latest    d6414b470cf2   2 months ago 

[vvstubbs]

I had this issue but I forwarded it to another port

services:
dockerproxy:
image: ghcr.io/tecnativa/docker-socket-proxy:latest
container_name: dockerproxy
privileged: true
environment:
- CONTAINERS=1 # Allow access to viewing containers
- SERVICES=1 # Allow access to viewing services (necessary when using Docker Swarm)
- TASKS=1 # Allow access to viewing tasks (necessary when using Docker Swarm)
- POST=1 # Disallow any POST operations (effectively read-only)
- LOG_LEVEL=info # debug,info,notice,warning,err,crit,alert,emerg
- IAMGES=1
- INF0=1
- NETWORKS=1
#- NODES=1
ports:
- 2376:2375
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro # Mounted as read-only
- /var/lib/haproxy/server-state:/var/lib/haproxy/server-state
restart: unless-stopped

[artemtech]

also happened to me. But after updating to the latest image, issue was fixed.

tecnativa/docker-socket-proxy                                          latest             1484f9fee8a7   2 weeks ago    19.3MB

using below config:

  docker-proxy:
    image: tecnativa/docker-socket-proxy
    container_name: socket-proxy
    restart: always
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      CONTAINERS: 1
      DISABLE_IPV6: 1
    networks:
      mynetwork.docker.local:

[pedrobaeza]

Yes, the HAProxy version change that provoked it was reverted, so closing