Can t connect to docker from docker-compose

Question

I installed docker-machine 0 1 0 and docker-compose 1 1 0 on Mac OS 10 8 5 Docker-machine is running normally and able to connect by docker-machine ssh     docker-machine ls NAME   ACTIVE   DRIVER       STATE     URL                         SWARM dev             virtualbox   Running   tcp   192 168 99 100 2376      However can t connect from docker-compose     docker-compose up      Couldn t connect to Docker daemon at http unix   var run docker sock - is it running       If it s at a non-standard location  specify the URL with the DOCKER HOST environment variable    My Dockerfile and docker-compose yml is here   Dockerfile  FROM centos centos7 DOCKER HOST tcp   192 168 99 100 2376   docker-compose yml  web    build      Why can t connect  Any ideas

User · Answer

Answer from  srfrnk works for me   In my situation  I had the next docker-compose yml file     nginx      build        context           dockerfile     docker nginx staging Dockerfile      depends on        - scripts     environment        NGINX SERVER NAME   some host        NGINX STATIC CONTENT OPEN FILE CACHE   off        NGINX ERROR LOG LEVEL  debug       NGINX BACKEND HOST  scripts       NGINX SERVER ROOT   var www html     volumes        -   docker-runtime drupal files  var www html sites default files rw     ports        - 80 80     docker-runtime owner and group - is root when the other files owner - my user  When I tried to build nginx   Couldn t connect to Docker daemon at http docker   localunixsocket - is it running    I added   docker-runtime to  dockerignore and it is solved my problem

User · Answer

I ve had the same symptoms   Only diff that it happened only during docker-compose build docker ps worked  Happened with version 2 x as well as 3 x  Restarted docker service  then the machine    Even re-installed docker   docker-compose   Tried everything but nothing helped   Finally I tried building the Dockerfile  manually  by using docker build   Apparently I had a permission issue on a file folder inside the Docker context  It was trying to read the context when starting the build and failed with a proper error message  However this error message did not propagate to docker-compose which only shows Couldn t connect to Docker daemon at http unix   var run docker sock - is it running   Having found that the solution was simply adding the file folder to the  dockerignore file since it wasn t needed for the build  Another solution might have been to chown or chmod it   Anyway maybe this could help someone coming across the same issue that really has nothing to do with docker and the misleading error message being displayed

User · Answer

The following worked for me  I m not sure what part did the trick  julian project  sudo service docker status julian varys  sudo service docker status                                                                                                                                                                                   docker service - Docker Application Container Engine    Loaded  loaded   lib systemd system docker service  enabled  vendor preset  enabled     Active  active  running  since Wed 2020-07-15 01 21 16 UTC  24min ago      Docs  https   docs docker com  Main PID  6762  dockerd      Tasks  25    CGroup   system slice docker service             -6762  usr bin dockerd -H fd    --containerd  run containerd containerd sock  julian project  export DOCKER HOST unix    run containerd containerd sock  julian project  sudo groupadd docker groupadd  group  docker  already exists julian project  sudo gpasswd -a  USER docker Adding user ubuntu to group docker julian project  newgrp docker  julian project  ls -ln  var run    grep docker drwx------  5   0   0  120 Jul 15 01 10 docker -rw-r--r--  1   0   0    4 Jul 15 01 10 docker pid srw-rw----  1   0 999    0 Jul 15 01 10 docker sock  julian project  sudo rm  var run docker sock                                                                                                                                                                                             julian project  sudo rm  var run docker pid  julian project  sudo service docker restart

User · Answer

I know it s silly  but in my case I just tried with sudo and it worked like a charm   in your case  just try    sudo docker-compose up

User · Answer

if you are using linux try sudo docker-compose up

User · Answer

while running docker-compose pull - i was getting below error     ERROR  Couldn t connect to Docker daemon at http docker   localhost   is it running   solution -   sudo service docker start    issue resolved

User · Answer

1   sudo service docker stop  2   sudo service docker status 3   sudo service docker start 4   docker-compose build  lt app name service name gt

User · Answer

Simple solution for me    sudo docker-compose up    UPDATE 2016-3-14   At some point in the docker install process  or docker-compose    there is a suggestion and example to add your username to the  docker  group   This allows you to avoid needing  sudo  before all docker commands  like so      gt  docker run -it ubuntu  bin bash root 665d1ea76b8d    date Mon Mar 14 23 43 36 UTC 2016 root 665d1ea76b8d    exit exit    gt     Look carefully at the output of the install commands  both docker  amp  the 2nd install for docker-compose  and you ll find the necessary step   It is also documented here   https   subosito com posts docker-tips      Sudo  No       Tired of typing sudo docker everytime you issue a command  Yeah  there   is a way for dealing with that  Although naturally docker is require a   root user  we can give a root-equivalent group for docker operations       You can create a group called docker  then add desired user to that   group  After restarting docker service  the user will no need to type   sudo each time do docker operations  How it looks like on a shell   commands  as a root  here you go     gt  sudo groupadd docker  gt  sudo gpasswd -a username docker  gt  sudo service docker restart       Done    UPDATE 2017-3-9  Docker installation instructions have been updated here   Post-installation steps for Linux  This section contains optional procedures for configuring Linux hosts to work better with Docker   Manage Docker as a non-root user  The docker daemon binds to a Unix socket instead of a TCP port  By default that Unix socket is owned by the user root and other users can only access it using sudo  The docker daemon always runs as the root user   If you don   t want to use sudo when you use the docker command  create a Unix group called docker and add users to it  When the docker daemon starts  it makes the ownership of the Unix socket read writable by the docker group   To create the docker group and add your user     1  Create the docker group    sudo groupadd docker    2  Add your user to the docker group    sudo usermod -aG docker  USER    3  Log out and log back in so that your group membership is re-evaluated     4  Verify that you can run docker commands without sudo    docker run hello-world   This command downloads a test image and runs it in a container  When the container runs  it prints an informational message and exits

User · Answer

try this   sudo ln -s  usr local bin docker-compose  usr bin docker-compose

User · Answer

For me  I started upgrading Docker and cancelled midway  I didn t notice that Docker was not running  if it was  there is an icon at the top nav bar of my Macbook  by the battery remaining  time  etc   Once I launched it  and finished the upgrade  docker-compose up worked again

User · Answer

sudo docker-compose up  I did follow the steps as it is in the above answer to add  USER to group docker  i didn t want to add a new group docker because in my docker installation a group named docker automatically created   Docker CE is installed and running  The docker group is created but no users are added to it  You need to use sudo to run Docker commands  Continue to Linux postinstall to allow non-privileged users to run Docker commands and for other optional configuration steps    but using docker-compose up didn t work either  It gave the same previous error  So in my case Ubuntu 18 10  sudo docker-compose up fixed the issue   ps   Tiw thanks for the advice

User · Answer

Try running dockerd or sudo dockerdif required first to start daemon  If you start dockerd with sudo you may want to run docker-compose up with sudo also  otherwise it s fine   Working solution from https   github com docker compose issues 4181

User · Answer

if you are using docker-machine then you have to activate the environment using env  variable  incase you are not using docker-machine then run your commands with sudo

User · Answer

The Docker machine is running  But you need to export some environment to connect to the Docker machine  By default  the docker CLI client is trying to communicate to the daemon using http unix   var run docker sock  as shown in the error message    Export the correct environment variables using eval   docker-machine env dev  and then try again  You can also just run docker-machine env dev to see the environment variables it will export  Notice that one of them is DOCKER HOST  just as the error message suggests you may need to set

User · Answer

Anyone checked log    In my case error message in  var log upstart docker log was   Listening for HTTP on unix   var run docker sock    graphdriver  using prior storage driver  aufs   Running modprobe bridge nf nat failed with message    error  exit status 1  Error starting daemon  Error initializing network controller  Error creating default  bridge  network  can t find an address range for interface  docker0     Worth to mentioned I had vpn turned on  so     sudo service openvpn stop   sudo service docker restart   docker-compose up start   sudo service openvpn start  was the solution

User · Answer

logging out then in again helped me  In my case it was fresh install  I created a new user  new group then added the user to the docker group  exit exit then ssh into the server again

User · Answer

By default the docker daemon always runs as the root user  therefore you need to prepend sudo to your Docker command s    If you don   t want to use sudo when you use the docker command  create a Unix group called docker and add users to it  When the docker daemon starts  it makes the ownership of the Unix socket read writable by the docker group   To create the docker group and add your user    Create the docker group      sudo groupadd docker Add your user to the docker group     sudo usermod -aG docker  USER Log out and log back in so that your group membership is re-evaluated  Verify that you can docker commands without sudo     docker run hello-world   This command downloads a test image and runs it in a container  When the container runs  it prints an informational message and exits   The steps outlined above comes from the official Docker documentation

User · Answer

sudo systemctl start docker  - to start the Docker service   sudo docker-compose up after that   I have Fedora 26  and trying to solve the same issue I eventually entered Docker Compose on Fedora Developers  page and then Docker on Fedora Developers  page  which helped me   Probably  docker service considered by community to start with the system and run in background all the time  but for me it was not so obvious  and that s the reason I can think of why there s no popular answer like this one   On the Fedora Developers  page there s instruction how to enable Docker to start with the system   sudo systemctl enable docker

User · Answer

WORKING   I tried with below commands and its working service docker restart docker-compose -f docker compose yaml down docker-compose -f docker compose yaml up

User · Answer

I solved the issue in Ubuntu 20 0 4 by sudo chmod 666  var run docker sock  and then sudo service docker start  amp  amp  docker-compose up -d  Ref

User · Answer

When you get an Error      ERROR  Couldn t connect to Docker daemon at http docker   localhost -   is it running    The Solution would be    First  try verifying Docker Service is Up and Running as expected on your remote local machine sudo service docker status  if Not - run sudo service docker start  or sudo systemctl start docker  depends on some linux versions  see Docker get started instructions   Second  start docker as sudo sudo docker-compose up

User · Answer

If you are on Linux you may not have docker-machine installed since it is only installed by default on Windows and Mac computers   If so you will need to got to  https   docs docker com machine install-machine  to find instructions for how to install it on your version of Linux   After installing  retry running docker-compose up before trying anything listed above   Hope this helps someone   This worked for my devilbox installation in Fedora 25

User · Answer

I have resolved the issue using following steps    sudo service docker status   sudo service docker start   sudo docker-compose up   now docker-compose up is working

User · Answer

If you started docker using sudo   then you should run docker-compose up with sudo Like  sudo docker-compose up

User · Answer

Apart from adding users to docker group  to avoid typing sudo repetitively   you can also create an alias for docker commands like so   alias docker-compose  sudo docker-compose  alias docker  sudo docker

User · Answer

Try restarting your docker environment using  systemctl restart docker

User · Answer

My setup has got two cases for this error      pycache   files created by root user after I run integration tests inside container are inaccessible for docker  tells you original problem  and docker-compose  tells you about docker host ambiguously   microk8s blocked my port until I stopped it

[docker] Can't connect to docker from docker-compose

Examples related to docker

Examples related to docker-compose