-
Notifications
You must be signed in to change notification settings - Fork 1.1k
docker-compose.yml does not work #280
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
Comments
Try and check the logs to see what might have gone wrong with |
Thanks for that, but here's the result and logs:
|
Judging by the logs it just seems like a simple wrong password issue. I know it's unlikely but have you doubled checked that in your yml config the passwords do match? |
Also if you changed the database password env in the yaml, you need to delete the database container and volume for the change to take (since it is only used on first initialization) See docker-library/postgres#203 (comment) for info about a volume on a database when using compose. |
Closing since this appears to be an issue with your environment or setup (and we can't reproduce). In the future, these sorts of questions/requests would be more appropriately posted to the Docker Community Forums, the Docker Community Slack, or Stack Overflow. |
I just simply followed: https://hub.docker.com/r/_/wordpress/
section: "... via docker stack deploy or docker-compose"
I've setup my docker-compose in ubuntu 16.04
version is:
docker-compose version 1.16.1, build 6d1ac21
Then I run
docker-compose stack.yml up -d
.Then I can see two container lauched:
But if I go to browser:
localhost:8081
This site can’t be reached
is displayed.sigh
The text was updated successfully, but these errors were encountered: