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

dockeratom_mysql_1 fails to run out of the box #2

Open
ravn opened this issue Nov 9, 2015 · 2 comments
Open

dockeratom_mysql_1 fails to run out of the box #2

ravn opened this issue Nov 9, 2015 · 2 comments
Assignees

Comments

@ravn
Copy link

ravn commented Nov 9, 2015

I'm trying to get this up and running on a fresh checkout on Ubuntu 15.10 with the latest docker and docker-compose.

After cleaning with "docker-compose rm", I ran "docker-compose build" - which completes without any errors, and then "docker-compose up". This gave the following error:

tra@PC599:~/git/docker-atom$ docker-compose up
Creating dockeratom_elasticsearch_1
Creating dockeratom_mysql_1
Creating dockeratom_nginx_1
ERROR: Cannot start container 43729b9ef7a5505db30164f1e4bcff73fca2b065fb46c234edfefecc5ed3cf56: Cannot link to a non running container: /dockeratom_mysql_1 AS /dockeratom_nginx_1/mysql_1

Running docker-compose up again starts the containers but the db instance fails with "dockeratom_mysql_1 exited with code 1". This might be related to the earlier log lines which hints that mysqld is not available.

tra@PC599:~/git/docker-atom$ docker-compose up
dockeratom_elasticsearch_1 is up-to-date
Starting dockeratom_mysql_1
Starting dockeratom_nginx_1
Attaching to dockeratom_elasticsearch_1, dockeratom_mysql_1, dockeratom_nginx_1
mysql_1         | 2015-11-09 12:57:16Running mysql_install_db ...
mysql_1         |  [ERROR]   Can't locate the server executable (mysqld).
mysql_1         | 2015-11-09 12:57:16 [WARNING] mysql_install_db is deprecated. Please consider switching to mysqld --initialize
elasticsearch_1 | [2015-11-09 12:54:37,671][INFO ][node                     ] [Iron Lad] version[2.0.0], pid[1], build[de54438/2015-10-22T08:09:48Z]

I am as yet unfamiliar with Docker. How should I fix this?

(also it appears that the webinterface now runs on port 80, not 8000 as indicated in the README - this might also be me not doing things correctly).

@jbfink jbfink self-assigned this Nov 27, 2015
@jbfink
Copy link
Owner

jbfink commented Nov 27, 2015

Hi @ravn! Sorry I didn't see this until just now. I've changed some things -- could you pull the latest version and try again? I'll also run it a few times on my end. Would you mind reporting what version of docker-compose and docker you're running? Latest Docker is 1.9.1, latest Compose is 1.5.1.

@jbfink
Copy link
Owner

jbfink commented Nov 27, 2015

Also -- do you mean the web interface runs on port 80 on the host computer? Viz, you go to http://hostname-of-docker-server:80 and you get the interface? That is very strange -- you can see in the docker-compose.yml the ports: "8000:80" statement. So I wonder if there's something very odd in your docker and/or docker compose install.

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