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
Unknown database, mysql database and user does not exist...? #1017
Comments
Can you post your Docker logs from the MySQL container? |
I'm noticing that i can change this ONLY on the first run. Subsequent builds/runs fail to update with these new values, and retain the first run (regardless of removing volumes, containers, images). |
@ItaloBC @iredmedia I am having the same problem, it seems that one of the commits removed all the ENV commands from the mysql Dockerfile: |
environment variables were removed from
…d added startup file back
The issue in my case is that CHANGING after FIRST run, the DB still exists on the host OS and isn't modified as per #1028. Need to manually change info, or delete ~/.laradock/data/[mysql/postgres] etc. in the .env file
|
fixed issue #1017, added ENV variables back to Dockerfile and added …
…d added startup file back
fixed issue laradock#1017, added ENV variables back to Dockerfile and added …
Info:
$ docker --version
): Docker version 17.03.1-ce, build c6d412e$ git rev-parse HEAD
): ab464d9Issue:
What seems to be going wrong?
It seems like there is no database nor user created for the mysql server.
The server is up and running but there are no database called "homestead" or what ever i add in my .env
Expected behavior:
What should be happening instead?
A database and a user should be created
Reproduce:
How might we be able to reproduce the error?
I follow basic getting started instrucitons, add laradock as an git submodule.
I run:
docker-compose up -d nginx mysql
Relevant Code:
Laravel .env (changed
DB_HOST
tomysql
Laradock .env (default)
The text was updated successfully, but these errors were encountered: