Failed to start docker-proxy, check that the current version is in your $PATH

Docker Engine General
1

Hi there!

as per failed to start docker-proxy, check that the current version is in your $PATH · Issue #6023 · docker/cli · GitHub

Strange error on new version exposing a port via docker -p. Searched for issues but nothing quite like this; fresh install

 Linux myhost 6.11.0-24-generic #24~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 25 20:14:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

port is not in use returns empty

netstat -tulpn | grep 1883

docker run --rm -p 1883:1883 jllopis/mosquitto

Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint mqtt-1 (85ab20e55685df71bcf18d24f1f6a86b0a4f5746f4fad08b4642b5b610407e99): failed to start userland proxy for port mapping 0.0.0.0:1883:172.22.0.6:1883/tcp: failed to start docker-proxy, check that the current version is in your $PATH

is present and on $PATH

    /usr/bin/docker-proxy
    /usr/local/bin/docker-proxy
    /usr/local/docker-19.03.9/bin/docker-proxy

Client: Docker Engine - Community
     Version:           19.03.9
     API version:       1.40
     Go version:        go1.13.10
     Git commit:        9d988398e7
     Built:             Fri May 15 00:22:47 2020
     OS/Arch:           linux/amd64
     Experimental:      false

    Server: Docker Engine - Community
     Engine:
      Version:          28.1.0
      API version:      1.49 (minimum version 1.24)
      Go version:       go1.23.8
      Git commit:       3f46cad
      Built:            Thu Apr 17 09:54:54 2025
      OS/Arch:          linux/amd64
      Experimental:     false
     containerd:
      Version:          1.7.27
      GitCommit:        05044ec0a9a75232cad458027ca83437aae3f4da
     runc:
      Version:          1.0.0-rc10
      GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
     docker-init:
      Version:          0.19.0
      GitCommit:        de40ad0

Client:
     Debug Mode: false
     Plugins:
      buildx: Docker Buildx (Docker Inc., v0.22.0)
      compose: Docker Compose (Docker Inc., v2.35.0)

    Server:
     Containers: 11
      Running: 7
      Paused: 0
      Stopped: 4
     Images: 8
     Server Version: 28.1.0
     Storage Driver: overlay2
      Backing Filesystem: extfs
      Supports d_type: true
      Using metacopy: false
      Native Overlay Diff: true
      userxattr: false
     Logging Driver: json-file
     Cgroup Driver: systemd
     Plugins:
      Volume: local
      Network: bridge host ipvlan macvlan null overlay
      Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
     Swarm: inactive
     Runtimes: runc io.containerd.runc.v2
     Default Runtime: runc
     Init Binary: docker-init
     containerd version: 05044ec0a9a75232cad458027ca83437aae3f4da
     runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
     init version: de40ad0
     Security Options:
      apparmor
      seccomp
      WARNING: You're not using the default seccomp profile
       Profile: builtin
      cgroupns
     Kernel Version: 6.11.0-24-generic
     Operating System: Ubuntu 24.04.2 LTS
     OSType: linux
     Architecture: x86_64
     CPUs: 4
     Total Memory: 7.589GiB
     Name: myhost
     ID: 08bf92c2-982c-4390-b86f-2aba70596cb7
     Docker Root Dir: /var/lib/docker
     Debug Mode: false
     Registry: https://index.docker.io/v1/
     Labels:
     Experimental: false
     Insecure Registries:
      ::1/128
      127.0.0.0/8
     Live Restore Enabled: false

    WARNING: No kernel memory limit support
    WARNING: No oom kill disable support
    WARNING: bridge-nf-call-iptables is disabled
    WARNING: bridge-nf-call-ip6tables is disabled
2

I manually added

ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock --userland-proxy-path=/usr/local/bin/docker-proxy

Still no joy.. I guess docker on nobel is a bit broken?

tried it with podman compose.. seems to work.

3

Answered in the github ticket.. was an old version that was preinstalled. purged it and were back in business thanks to @thaJeztah

as per failed to start docker-proxy, check that the current version is in your $PATH · Issue #6023 · docker/cli · GitHub

1 Like
4

Can you share the link to the github issue, so others that might have the same problem, can see the actual solution? And mark that post as solution?

Update: I just noticed that you already share the link in your first post. So the only thing left to do is to mark your last post as solution :slight_smile:

1 Like
5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.