I installed docker on my ubuntu 14.04. deamon is running. but when I run
docker ps -a
i got this error -bash: /usr/local/bin/docker: No such file or directory
How can I solve this?
Thanks in advance
Asked
Active
Viewed 1.3k times
5
Felix
- 5,452
- 12
- 68
- 163
-
what is the result of `find / -type f -name docker` – Romeo Ninov Jan 15 '19 at 11:34
-
1FYI on my Ubuntu it is `/usr/bin/docker` – grapes Jan 15 '19 at 11:35
-
Can you show output of `which docker`? – funnydman Jan 15 '19 at 11:45
-
it says /usr/bin/docker – Felix Jan 15 '19 at 11:53
-
1I don't understand why `docker` command resolves to `/usr/local/bin/docker`, since `docker` is located in `/usr/bin`. Do you have an alias in your `.profile` or something like that? Is it a fresh install? Have `docker` been installed before? – norbjd Jan 15 '19 at 12:12
-
hmmm how can I fix it? it was a clean install – Felix Jan 15 '19 at 12:14
-
I'm getting the same error `-bash: /usr/local/bin/docker: No such file or directory` – Bynd Sep 30 '19 at 02:13
2 Answers
11
A quick fix can be adding a symbolic link (/usr/bin/docker -> /usr/local/bin/docker) :
ln -s /usr/bin/docker /usr/local/bin/docker
norbjd
- 10,166
- 4
- 45
- 80
-
then I got this: `-bash: /usr/local/bin/docker: Too many levels of symbolic links` – Felix Jan 15 '19 at 14:09
-
If you have run the command in the deleted answer (**DO NOT RUN THIS** : `ln -sf /usr/local/bin/docker /usr/bin/docker`), then your `/usr/bin/docker` have been corrupted (the deleted answer defined arguments of `ln` in the wrong order, so `/usr/bin/docker` points to `/usr/local/bin/docker` that does not exist). So I'm afraid you have to reinstall Docker, and then run the command I gave (with arguments in the right order :p). – norbjd Jan 15 '19 at 14:52
-
ok now I got this: `Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?` when I check the status: `sudo /etc/init.d/docker status docker stop/waiting` – Felix Jan 15 '19 at 15:24
-
Is `docker` daemon started? If not, start it. Is your user in `docker` group? If not, try `sudo docker info`. – norbjd Jan 15 '19 at 15:27
-
-
found this issues: ERRO[2019-01-15T16:02:49.091537567Z] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded. storage-driver=overlay2 ERRO[2019-01-15T16:02:49.092716333Z] AUFS was not found in /proc/filesystems storage-driver=aufs ERRO[2019-01-15T16:02:49.093831844Z] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded. storage-driver=overlay – Felix Jan 15 '19 at 16:03
-
I suggest you to create a new question for this and close this one, since it is an other issue. – norbjd Jan 15 '19 at 16:24
0
Run the following in your terminal:
dockerd
Explanation: dockerd is the persistent process that manages containers. Docker uses different binaries for the daemon and client. To run the daemon you type dockerd.
To run the daemon with debug output, use dockerd -D or add "debug": true to the daemon.json file.
Reference: https://docs.docker.com/engine/reference/commandline/dockerd/
Diablo
- 426
- 6
- 10