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
Diagnostic check throws an error that the db is not running.
App server container can’t connect to db container by addressing with
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: