Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

exec: "docker-proxy": executable file not found in $PATH

See original GitHub issue

When I run docker-compose up -d on a compose file that works with docker-desktop I get the following responses in container-desktop:

➜  docker git:(main) docker-compose up -d
[+] Running 0/1
 ⠦ Container proxy  Starting                                                                                       0.7s
Error response from daemon: driver failed programming external connectivity on endpoint proxy (b981cc53a782cf84ce46a9f64106f7e65035a617f419476e30a58fb11e812e7e): exec: "docker-proxy": executable file not found in $PATH

➜  docker git:(main) docker-compose up -d
[+] Running 0/1
 ⠹ Container proxy  Starting                                                                                       0.2s
Error response from daemon: driver failed programming external connectivity on endpoint proxy (aef093e5c0727b448bb0c5bc2077e48b4ce59a8a95e3b7b25f63e69153ecc57d): Bind for 0.0.0.0:8080 failed: port is already allocated

I’m getting this result every time I run docker-compose up -d from a fresh boot. First it errors with docker-proxy cannot be found exactly once, and every subsequent docker-compose up errors with port is already allocated.

This is from a fresh boot where docker-desktop has not been started and where I have deleted all docker-desktop wsl distros. Netstat does not show port 8080 as being bound by anything in windows or in my WSL distro.

When then killing container-desktop and starting docker-desktop the port binding of that container works fine.

I can share the compose file if necessary, but it’s nothing special. It spins up traefik proxy to listen on port 443 and traefik dashboard on 8080. Then it starts some webservices that are accessible through traefik.

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:15 (6 by maintainers)

Top GitHub Comments

2reactions

erwinkerstencommented, May 2, 2022

container-desktop distribution doesn’t have execute permission on the file docker-proxy in /usr/local/bin/. This happens when the users enables the port-forwarding option, then container desktops replaces the docker-proxy with the docker-proxy-shim version which doesn’t have execute permission. Will provide a fix.

1reaction

markrexwinkelcommented, Jan 25, 2022

container-desktop is deployed as its own distribution and therefore is completely isolated from docker-desktop. It runs its own deamon, so everything you do on docker-desktop is not visible to container-desktop and visa versa.

Top Results From Across the Web

1627907 – docker-proxy executable not found in $PATH

I fixed the problem by the following command: ln -sf /usr/libexec/docker/docker-proxy-current /usr/libexec/docker/docker-proxy Version-Release number of ...

How to enable docker-proxy

Docker -proxy is a executable file after docker engine installation, just like dockerd. So maybe you should try it with root, or chmod...

docker exec's "executable file not found in $PATH" should ...

Description When docker exec cannot find an executable it prints an error. This error should go to standard error (stderr).

[2/2] docker-engine: add dependency on docker-proxy

... connectivity on endpoint: exec: "docker-proxy": executable file not found in $PATH. Docker expects the docker-proxy binary to exist in the PATH.

Linux – How to enable docker-proxy

I am trying to install a docker package following this instruction. ... exec: "docker-proxy": executable file not found in $PATH.