-
Notifications
You must be signed in to change notification settings - Fork 41
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
autopilotpattern/mysql:latest didn't work for me. #42
Comments
@khangngu: can you say what errors you encountered before you changed the MySQL image tag? |
Sorry I wasn't able to detect the exact error or find any useful clue in the log files. But I noticed that the wordpress autopilot only worked for me on one of the datacenters where I already had the image "autopilotpattern/mysql:5.6r3.1.0". On the other datacenters where the newer image "autopilotpattern/mysql:latest" was pulled, the wordpress deployment didn't work. The mysql instance was created successfully, but it looked like mysql database was not set up correctly. After I modified the docker-compose.yml file, the deployment for wordpress autopilot worked on the datacenters where it didn't work before. |
I had the same issue. Watching the logs (stdout of mysql) there was a stream of errors. Changing to the version, indicated above, solved the issue. |
We probably should pin the version. The |
To get the wordpress autopilot to work successfully, I had to modify the docker-compose.yml file to use "autopilotpattern/mysql:5.6r3.1.0".
The text was updated successfully, but these errors were encountered: