Driver error: db is not running

Expected behavior

Diagnostic check should be all good . Also, when I run docker-compose with linked containers, I should be able to address these containers by their name (in my case I have a postgres database running in a container named psql and I try to connect to this container from another with the URL psql://

Actual behavior

Diagnostic check throws an error that the db is not running.

App server container can’t connect to db container by addressing with psql://.

Information

Diagnostic ID: 1DB51AA2-0B9B-43B0-8F60-8C8B119CA78C

Docker for Mac: version: mac-v1.12.0-beta16.2
OS X: version 10.11.4 (build: 15E65)
logs: /tmp/20160618-204809.tar.gz
failure: Docker.app/Contents/MacOS/com.docker.driver.amd64-linux -db is not running
[OK]     docker-cli
[OK]     app
[OK]     menubar
[OK]     virtualization
[OK]     system
[OK]     osxfs
[OK]     db
[OK]     slirp
[OK]     moby-console
[OK]     logs
[OK]     vmnetd
[OK]     env
[OK]     moby
[ERROR]  driver.amd64-linux
         Docker.app/Contents/MacOS/com.docker.driver.amd64-linux -db is not running

Here is an example of my Dockerrun.aws.json file (the file AWS elasticbeanstalk uses to generate a Docker compose file): http://cl.ly/2d0s0z033q3s

Steps to reproduce the behavior

First issue: run diagnostic check.

Second (probably related) issue: docker-compose.

Bump. Is anyone else experiencing this? My Docker just updated itself, and I can’t find the old version. Gotta go back to an old version I backed up on Dropbox. :frowning:

Nevermind - the problem seems to have gone away (not being able to connect to the psql container) with this new upgrade. My guess is that it stems from me updating awsebcli actually. Although the diagnostic check still fails in the same way.

Docker for Mac: version: mac-v1.11.2-beta15
OS X: version 10.11.4 (build: 15E65)
logs: /tmp/20160621-001205.tar.gz
failure: Docker.app/Contents/MacOS/com.docker.driver.amd64-linux -db is not running
[OK]     docker-cli
[OK]     app
[OK]     menubar
[OK]     virtualization
[OK]     system
[OK]     osxfs
[OK]     db
[OK]     slirp
[OK]     moby-console
[OK]     logs
[OK]     vmnetd
[OK]     env
[OK]     moby
[ERROR]  driver.amd64-linux
         Docker.app/Contents/MacOS/com.docker.driver.amd64-linux -db is not running

This seems to have surfaced again in this recent update of Docker to a public beta.

Docker for Mac: version: mac-v1.12.0-beta17
OS X: version 10.11.4 (build: 15E65)
logs: /tmp/20160630-172820.tar.gz
[OK]     docker-cli
[OK]     app
[OK]     menubar
[OK]     virtualization
[OK]     system
[OK]     osxfs
[OK]     db
[OK]     slirp
[OK]     moby-console
[OK]     logs
[OK]     vmnetd
[OK]     env
[OK]     moby
[OK]     driver.amd64-linux

Diagnostic ID is 67865CED-FF62-45E8-90B5-17862542AD14.

This is the error I see (from an ORM library trying to connect to a DB via psql:// as the URL prefix):

opentest_1 | could not connect to db: { [SequelizeHostNotFoundError: getaddrinfo ENOTFOUND psql psql:5432]
opentest_1 |   name: 'SequelizeHostNotFoundError',
opentest_1 |   message: 'getaddrinfo ENOTFOUND psql psql:5432',
opentest_1 |   parent:
opentest_1 |    { [Error: getaddrinfo ENOTFOUND psql psql:5432]
opentest_1 |      code: 'ENOTFOUND',
opentest_1 |      errno: 'ENOTFOUND',
opentest_1 |      syscall: 'getaddrinfo',
opentest_1 |      hostname: 'psql',
opentest_1 |      host: 'psql',
opentest_1 |      port: 5432 },