-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
Fix running addon when using zfs as backing storage #21
Conversation
💖 Thanks for opening this pull request! 💖 If your PR gets accepted and merged in, we will invite you to the project 🎉 |
Let's do it! |
Congrats on merging your first pull request! 🎉🎉🎉 |
Was this merge included in the dockerimage cut 8 days ago? (0.3.1). I'm having the same issue, and it looks like the image still tries to create INNODB files: `Add-on version: 0.3.1 ` Thanks! |
It has been reverted and cannot be done. |
Understood, thank you for the clarification! Maybe we can change the mysql backend requirement like was done with BitwardenRS... (see I listened to your latest podcast! ;) ) I'll check if that is feasible. Thx, G, |
I think this Pull request in nginx-proxy-manager might be fixing our issue with running docker on zfs, by implementing an SQLite version (or db-selectable at least): NginxProxyManager/nginx-proxy-manager#256 We'll just have to wait a bit. G. |
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
Proposed Changes
Drop innodb support
Short story, when using zfs and bind mounts for volumes innodb craps out on creating the ibdata1 file
Because i didn't find any usage of innodb, i think the easiest solution is just disabling i
Related Issues
https://bugs.alpinelinux.org/issues/9046
https://jira.mariadb.org/browse/MDEV-16015