-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Deadlock problem with mariadb:latest (docker) #11841
Comments
Thank you for the feedback. Yes, there are some issues with the latest mariadb as the |
Of course, it isn't hard but if nobody tells you it is very hard to find the reason of that problem. Even at the moment all examples and tutorials says you should install mariadb:latest (although that can't run correct) |
Good point. Could you please file a ticket at https://github.com/nextcloud/documentation/issues? |
Unless they are from the official Nextcloud documentation we can't do much about this. I suggest reporting this back to the tutorial publishers! |
The Docker-Repo is: https://github.com/nextcloud/docker I made this a long time ago: But nobody cares... |
Hi,
I used docker to setup my nextcloud service with nginx and fpm: https://github.com/nextcloud/docker/tree/master/.examples/docker-compose/with-nginx-proxy/mariadb-cron-redis/fpm
I had a lot of problems there with deadlocks: #11734 .
Now I realized, that the Deadlocks Errors, didn't occur with mariadb:10.0, mariadb:10.1, mariadb:10.2 and mariadb:10.3 .
They just occur with mariadb:latest image.
I don't know which version is included in mariadb:latest but I think it should be a new version.
So there must be a error in the newest mariadb implementation or in the newest nextcloud:fpm implementation or in the newest nextcloud documentation (settings for mariadb) .
I hope I could help somebody with this post. That issue cost me nearly 10 hours.
T
The text was updated successfully, but these errors were encountered: