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://.
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.
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