exec: "com.docker.cli": executable file not found in $PATH

Question

I am getting this error when docker-compose up on one of the containers only.

exec: "com.docker.cli": executable file not found in $PATH
The terminal process "/bin/zsh '-c', 'docker logs -f f6557b5dd19d9b2bc5a63a840464bc2b879d375fe72bc037d82a5358d4913119'" failed to launch (exit code: 1).

I uninstalled and reinstalled docker [email protected] on Mac
docker-compose build from scratch
other containers are running
I get the above error.
It used to be running. I am not sure why this is happening. I know that I upgraded docker from I think 2.3
also I think I received an update on my mac

Dockerfile

FROM tiangolo/uvicorn-gunicorn:python3.8
COPY requirements.txt /app/
RUN pip install -r requirements.txt

COPY ./app /app/app
#COPY config.py /app/app/

docker-compose.yml

version: "3"

services:
    postgresql:
        container_name: postgresql
        image: postgres:12
        ports:
            - "5433:5432"
        environment:
            - POSTGRES_USER=${POSTGRES_USER}
            - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
            - POSTGRES_DB=${POSTGRES_DB}
        volumes:
            - ./postgres-data:/var/lib/postgresql/data
    fastapi:
        build:
            context: ./fastapi/
            dockerfile: Dockerfile
        volumes:
            - ./fastapi/app/imgs:/app/app/imgs
        ports:
            - "1001:80"
        depends_on:
            - postgresql
        env_file:
            - .env
    pgadmin:
        container_name: pgadmin
        image: dpage/pgadmin4
        environment:
            - [email protected]
            - PGADMIN_DEFAULT_PASSWORD=admin
        ports:
            - "5050:80"
        depends_on:
            - postgresql

    solr:
        build:
            context: ./solr/
            dockerfile: Dockerfile
        restart: always
        ports:
            - "8983:8983"
        volumes:
            - data:/var/solr
volumes:
    data:

update: It worked when I downgraded to docker desktop 2.3.0.4

I had the same issue and downgrading to 2.3.0.4 helped me as well. I created this issue: github.com/docker/for-mac/issues/4956 But then I updated it again via automatic updates to version 2.4.0.0 and the second time it kept working. — RawChid
– RawChid, Commented Oct 1, 2020 at 18:35
I think dockerfile and docker-compose config are not related to the problem and should be excluded from the question. — skoval00
– skoval00, Commented Nov 10, 2020 at 17:11

Hannes Oberreiter · Accepted Answer · 2021-06-22 06:19:03Z

13

Updated Answer:

Since VSCode Docker 1.14.0 you can now set the Docker executable path in the settings, which should help in most cases.

Old Answer (Option was removed from Docker Desktop):

The Desktop Docker Version 2.4.0.0 is working for me after I did deactivate the feature Enable cloud experience. You can find it under Preferences --> Command Line.

If you are still experience the problem, you may try a clean remove and install of Docker and also make sure that Docker is actually running, see other possible solution(s) here.

History of GitHub Issues:

https://github.com/docker/for-mac/issues/4956
https://github.com/microsoft/vscode-docker/issues/2366
https://github.com/microsoft/vscode-docker/issues/2578
https://github.com/microsoft/vscode-docker/issues/2894
Status (2021-06-22): VSCode Version 1.57.0 seems to have fixed the issue again.

edited Jun 22, 2021 at 6:19

answered Oct 5, 2020 at 16:13

Hannes Oberreiter

6818 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

GuiFalourd Over a year ago

I confirm this solution works using MacOs Catalina 10.15.6, with Docker Desktop 3.1.0

karjedavpalaa Over a year ago

Does not work for me on Manjaro 21.3.7 Ruah with Docker Desktop 4.12.0

vintagexav · Accepted Answer · 2020-10-13 09:22:02Z

8

You might get the following error message simply because you did not start Docker just yet

exec: "com.docker.cli": executable file not found in $PATH

answered Oct 13, 2020 at 9:22

vintagexav

2,0572 gold badges20 silver badges22 bronze badges

1 Comment

MohammadBaqer Over a year ago

so how to start it

apokryfos · Accepted Answer · 2022-06-23 15:08:49Z

6

In my case the problem was I had installed and then crudely removed the docker compose cli. This resulted in the above error to start popping up.

I got the compose CLI back using instructions from https://docs.docker.com/cloud/ecs-integration/#install-the-docker-compose-cli-on-linux and running (as root):

curl -L https://raw.githubusercontent.com/docker/compose-cli/main/scripts/install/install_linux.sh | sh

This fixed it for me.

Note: I would not recommend installing docker-compose cli to fix this issue, but to share some insights in case this is applicable to you as well.

edited Jun 23, 2022 at 15:08

answered Jan 28, 2022 at 17:37

apokryfos

40.9k11 gold badges85 silver badges128 bronze badges

3 Comments

C. Smith Over a year ago

This fixed it for me, and IMO should be the solution.

Ate Somebits Over a year ago

@apokryfos the disclaimer note you've put in your answer creates a lot of questions

apokryfos Over a year ago

@AteSomebits to clarify what I mean. I encountered this problem because I had installed docker-compose and then removed it improperly and this solution should work in that case. If you never installed docker-compose in the past then installing it now will probably not solve the issue.

olusegvn · Accepted Answer · 2022-07-12 11:10:43Z

3

Ensure that docker CLI is installed not just docker desktop on Linux. YOu can install it using:

sudo apt install docker.io

answered Jul 12, 2022 at 11:10

olusegvn

313 bronze badges

Comments

Sujay · Accepted Answer · 2023-10-09 07:10:27Z

1

For those who may come with similar error for e.g.

exec: "com.docker.cli": executable file not found in $PATH Current PATH : XXXXXX

You may need to install the docker engine separately, atleast true in my case (using Arch linux). Thanks!

edited Oct 9, 2023 at 7:10

answered Oct 6, 2023 at 16:30

Sujay

4041 gold badge4 silver badges11 bronze badges

Comments

Kenny Trytek · Accepted Answer · 2021-03-17 15:08:12Z

0

Update: The "cloud experience" no longer exists even as an experimental feature in Docker Desktop v3.2.1. This should no longer be an issue.

If you continue to see this problem on a newer version, you will need to downgrade to Docker v3.1.0, disable the cloud experience feature, then upgrade to the newest version.

edited Mar 17, 2021 at 15:08

answered Mar 8, 2021 at 20:48

Kenny Trytek

413 bronze badges

Comments

eyllanesc · Accepted Answer · 2021-03-20 01:53:04Z

0

Had the exact same issue. Was fixed after starting the upgraded docker first, then running this command.

dostarr@DOSTARR-M-38LF ~ % docker run busybox
exec: "com.docker.cli": executable file not found in $PATH
<started docker>
dostarr@DOSTARR-M-38LF ~ % docker run busybox                           
dostarr@DOSTARR-M-38LF ~ %

edited Mar 20, 2021 at 1:53

eyllanesc

246k19 gold badges205 silver badges282 bronze badges

answered Mar 20, 2021 at 1:50

Doug

1

Comments

Amir Shitrit · Accepted Answer · 2022-01-20 10:34:45Z

0

I had the same problem when trying to run minikube tunnel, and since I didn't want to re-install anything, I ended up running it from the docker bin path (on Windows it's in 'C:\Program Files\Docker\Docker\resources\bin') and it worked.

answered Jan 20, 2022 at 10:34

Amir Shitrit

1,9022 gold badges12 silver badges7 bronze badges

Comments

mmsilviu · Accepted Answer · 2022-07-26 13:32:14Z

0

An alternative to Docker Desktop is colima, container runtimes on macOS (and Linux) with minimal setup.

# Homebrew
brew install colima docker

colima start

Now, you can use the docker commands as before.

For docker compose commands, you have to install:

brew install docker-compose

edited Jul 26, 2022 at 13:32

answered Jul 24, 2022 at 12:48

mmsilviu

1,5011 gold badge18 silver badges27 bronze badges

Comments

GarryOne · Accepted Answer · 2024-01-10 12:44:31Z

0

On Debian I had the exact same error after a manual binary installation.

Even if my binary was inside the /usr/bin which was already in the PATH, it still was not working. Running /usr/bin/docker was working though.

It turned out that I had the binary in both /usr/bin/docker and /usr/local/bin/docker.

I had to have instead a symlink between these 2 paths, rather than 2 independent binaries.

So I removed the /usr/local/bin/docker file and added instead a symlink from the /usr/bin/docker

ln -s /usr/bin/docker /usr/local/bin/docker

edited Jan 10, 2024 at 12:44

answered Jan 10, 2024 at 12:00

GarryOne

1,50817 silver badges21 bronze badges

Comments

Urvashi · Accepted Answer · 2020-10-21 05:12:01Z

-1

if already have installed docker, it may not have started. So type in terminal,"docker run -d -p 80:80 docker/getting-started" and it should solve the issue.

answered Oct 21, 2020 at 5:12

Urvashi

9

Collectives™ on Stack Overflow

exec: "com.docker.cli": executable file not found in $PATH

11 Answers 11

2 Comments

1 Comment

3 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

11 Answers 11

2 Comments

1 Comment

3 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related