Skip to content
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

MariaDB, Insecure, Apache Example is No Longer Working #951

Closed
ShiromMakkad opened this issue Dec 26, 2019 · 9 comments
Closed

MariaDB, Insecure, Apache Example is No Longer Working #951

ShiromMakkad opened this issue Dec 26, 2019 · 9 comments

Comments

@ShiromMakkad
Copy link

When I log in, it says that it cannot find the database. I'm using the exact code from the Github and I've set the database password.

The Postgress version works great, so I assume the issue is with the MariaDB docker image. It probably got changed in a recent update.

I'm just going to stick to Postgress, but I though you should know that the example is broken.

@jensamberg
Copy link

Hello,

I have the same problem MariaDB is not working

@ngoonee
Copy link

ngoonee commented Dec 27, 2019

Not just insecure, it's all the mariadb examples which aren't working. The version of mariadb should be specified in the example docker-compose.yml (IMHO).

@jensamberg
Copy link

I tried MariaDB 10.3 doesn’t work. Do anybody know the last working tag ?

@bigr4232
Copy link

bigr4232 commented Jan 2, 2020

It also is not working for me. Has anyone figured out a solution to this?

@ShiromMakkad
Copy link
Author

ShiromMakkad commented Jan 3, 2020

I got this same issue on jc21/nginx-proxy-manager. I fixed it by going to version 10.4.5, but for the downgrade to work, you had to delete all the persisted data inside the volumes. I'm not sure if @jensamberg did that, but it might be worth a shot here.

I think the issue is that MariaDB isn't reading the environment variables and they've changed the way you configure the database. I'm not sure what the new way is though.

@jensamberg
Copy link

@ShiromMakkad I tried a fresh installation. So I had no persist data. I also discovered that the MariaDB Image does not read the environment. Do you think the Issue is in the MariaDB Container?

@blackerking
Copy link

Got simmiliar problems with linuxserver/mariadb and linuxserver/nextcloud . I had to add a database and a user with privileges. Entering this information at start works. But i also had a timeout and I had to add the variable installed => true inside the config.

@Sincopy
Copy link

Sincopy commented Jan 23, 2020

It seems there's several regressions when doing first instantiation of MariaDB. One is related to the TZTIME tool timing out, but there's a workaround for that.
The second hurdle I found was (also on first instantiation) that writing to ibtmpl for some reason also took a very long time (10-15s) and timed out, even though it's only a 12mb file and dd-ing to the drive normally get's me about 400mbps. I gave up on mariadb after that.

Please also note that the yml files won't even work when replacing mariadb with mysql:latest, since none of the nextcloud images seem to include PHP7.4, required for the cached_sha256, which is default since mysql:8.
All in all, it would be smart to have the yml files pin the version of the images they were tested with, so at least examples work as published.

@J0WI
Copy link
Contributor

J0WI commented Jun 5, 2020

See MariaDB/mariadb-docker#262

@J0WI J0WI closed this as completed Jun 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants