Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection to Docker Daemon Drop #3016

Closed
shamil614 opened this issue Feb 24, 2016 · 5 comments
Closed

Connection to Docker Daemon Drop #3016

shamil614 opened this issue Feb 24, 2016 · 5 comments

Comments

@shamil614
Copy link

I'll have docker up and running with docker-compose up
All is fine. Then after about a minute, I see this
ERROR: Couldn't connect to Docker daemon - you might need to run docker-machine start default.

Running dockker-machine ls shows


NAME      ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER    ERRORS
default   *        virtualbox   Running   tcp://192.168.99.100:2376           v1.10.2

I can run docker-compose up again and it works for about another minute. Then connection drops.

docker -v
Docker version 1.10.2, build c3959b1
docker-compose -v
docker-compose version 1.6.0, build d99cad6
@dnephin
Copy link

dnephin commented Feb 24, 2016

I believe this is a duplicate of #2338.

It's possible to hit a timeout on the connection when a tty is used (possibly in other situations as well).

You can use up -d and logs as a workaround.

@shamil614
Copy link
Author

Thanks! I couldn't find a duplicate issue. I'll give it a try.

@shamil614
Copy link
Author

Dang. It still disconnected

partner-server 🍺  docker-compose up -d
partnerserver_web_1 is up-to-date
partnerserver_worker_1 is up-to-date
partner-server 🍺  docker-compose logs
Attaching to partnerserver_worker_1, partnerserver_web_1
web_1    | [8] Puma starting in cluster mode...
web_1    | [8] * Version 2.14.0 (ruby 2.2.4-p230), codename: Fuchsia Friday
web_1    | [8] * Min threads: 5, max threads: 5
web_1    | [8] * Environment: development
web_1    | [8] * Process workers: 1
web_1    | [8] * Phased restart available
web_1    | [8] * Listening on tcp://0.0.0.0:2000
web_1    | [8] Use Ctrl-C to stop
web_1    | [8] - Worker 0 (pid: 11) booted, phase: 0
worker_1 | I, [2016-02-25T00:01:31.604497 #1]  INFO -- : Rails app found at: ./config/environment.rb
worker_1 | I, [2016-02-25T00:01:44.240894 #1]  INFO -- : Starting ClientServer...
worker_1 | I, [2016-02-25T00:01:44.250111 #1]  INFO -- : Starting JobServer...
worker_1 | I, [2016-02-25T00:01:44.254340 #1]  INFO -- : Starting LocationServer...
worker_1 | I, [2016-02-25T00:01:44.259263 #1]  INFO -- : Starting OrganizationServer...
worker_1 | I, [2016-02-25T00:01:44.264375 #1]  INFO -- : Starting PartnerServer...
worker_1 | I, [2016-02-25T00:01:44.268823 #1]  INFO -- : Starting PromotionalCommissionPlanServer...
ERROR: Couldn't connect to Docker daemon - you might need to run `docker-machine start default`.

@shamil614
Copy link
Author

Looks like removing this from the docker-compose.yml file resolved it.

tty: true

@shamil614
Copy link
Author

In relation to this comment
#2338 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants