-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
Impossible to create instance with any database with separated containers #37
Comments
Hello, I will check |
Thanks a lot |
Hi, |
Sorry I haven't had time. I am going to check it this weekend |
Well the problem is that the plugin for PHP installed in the image is not compatible with MySQL 8. As with limesurvey 4 I need to redo the image to support the latest ubuntu and php7. For now I limited the version for MySQL to 5 in the docker-compose.yml: ...
services:
mysql:
image: mysql:5
volumes:
- mysql:/var/lib/mysql
restart: always
... You must delete everything in order for this change work in your containers with: docker-compose down --volumes Regards, |
Thanks a lot for the support, I used another survey tool this time but I am sure it will be useful for others and for me in the future. Just so you know there is probably still an issue with PostGreSQL. @rbeier feel free to close the issue if you don't have more questions and everything works on your side |
Hi Carlos, Greetings |
Hello,
I tried to create a docker-compose instance like you suggest on your main readme, in order to separate containers and use volumes.
However when I tried to use mysql I got the same problem as #32 . I also tried to modify the docker-compose to get a lower version of mysql but in this case the container keeps restarting and is unusable.
I then tried pgsql, the docker processes seem to start OK but when completing the admin user creation this gets throwed and it is impossible to continue.
Thanks in advance if you take the time to solve these issues.
The text was updated successfully, but these errors were encountered: