-
-
Notifications
You must be signed in to change notification settings - Fork 579
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
DB Container - Upgrade MariaDB to 10.2 #947
Comments
Totally agreed, but not sure when we can do it. We definitely want Mariadb 10.2. BUT... we use bind mounts of the database with this container. So the file actually exists on the host. On Windows, the underlying filesystem is NTFS. mariadb 10.2 (the package) absolutely doesn't work in docker with a bind mount to NTFS. We have an idea to test for a workaround (trying docker volume instead of a bind mount) (#714). It would be lovely if this works out. Mariadb has loads of weird problems on docker, it's quite odd. I'm leaving this open because it's a goal, but putting it to hibernate. |
As a sidenote, this docker-compose.db.yaml worked for me to get mariadb 10.2
|
The official container works except on Windows. So this technique might actually mostly work for you. You might want to just fork the contents of containers/mariadb-local and use mariadb:10.2 as the base. I don't think some of the startup behaviors of mysql will be handled the way you did this (like installing users and perms) but it's a pretty simple solution! Oh, I think you have an existing database; it probably wouldn't work with an initial project. |
Set this to actionable for v1.2.0; it may not be achievable, but with db now in docker volume, it may be possible. |
i used the following options to get around the key problem: .ddev/mysql/no_utf8mb4.cnf
|
When using DDEV with recent versions of Neos the mariadb version that comes with ddev is not sufficient since Maria 10.2 is requried.
I suggest to raise the version of the alpine-linux the db-container is based on from 3.7 to 3.8. Alpine 3.8 comes with MariaDB 10.2.15.
Alternatively some documentation on how a default mariadb:10.2 container can be used in ddev could solve the problem aswell.
The text was updated successfully, but these errors were encountered: