Fix #2165
To address https://github.com/nextcloud/docker/issues/2165
How about we keep 10.6 as the version (or update to 10.11), and still add --character-set-server=utf8 to be more explicit? Of course, only if this flag is supported by 10.6/10.11? This would take care of the problem in the future, in case Nextcloud starts supporting newer MariaDB versions and the issue is still the same then.
In my opinion, this is better than potentially running into the same issue again in the future. Worst case, someone has to analyse and fix this from scratch again because they won't find this issue right here.
Correct me if my view on this is wrong.
Edit: https://mariadb.com/docs/server/ref/cs10.6/character-sets/ supported charsets for 10.6 show utf8, so I guess the flag is fine
Edit 2: https://github.com/nextcloud/docker/issues/2165#issuecomment-1964160840 okay, never mind then! Issue is solved. Still, explicitly defining the charset can prevent this from happening again.
We may consider this again when this version is officially supported by Nextcloud but at the moment this is out of scope. There are already various ways to customize the images but we don't want to overload the examples to cover edge cases.