-
Notifications
You must be signed in to change notification settings - Fork 7
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
Web not connecting to the db on docker #92
Comments
Are there more logs? In theory this only happens if a previous migration crashed after creating the notes column |
I've run into the same error. The following steps are what I did to arrive there:
Logs: https://gist.github.com/PlatinPython/59a8c9c14d7904c1424cc377a003f789 Running Windows 10 Pro 22H2 and using the WSL 2 backend in docker. |
Hi @PlatinPython thank you very much for the detailed report. Based on the errors in the logs, I think you may be hitting MariaDB/mariadb-docker#331 (aka https://jira.mariadb.org/browse/MDEV-24189, aka microsoft/WSL#8443), which explains why I can't reproduce it on linux. Can you check whether the reproduction in microsoft/WSL#8443 (comment) applies to you? EDIT: Can you share more details on your docker setup? Are you on windows? Are you using the WSL-2 or the Hyper-V backend for docker / docker-desktop? Can you try the other one? |
As far as I can tell, the reproduction linked does not apply to me, as I don't get |
Docker with the Hyper-V backend seems to work fine. Login works and |
I initially used the bind mount because it's arguably easier to back up and move around than a volume, but turns out with DarkflameUniverse/NexusDashboard#92 it's nothing we can recommend for Docker Desktop on WSL, which unfortunately is the primary setup newcomers will try this with. So changing the default to be a volume should address that (presumably by hosting the volume within the WSL Docker VM, as opposed to the host NTFS filesystem)
I initially used the bind mount because it's arguably easier to back up and move around than a volume, but turns out with DarkflameUniverse/NexusDashboard#92 it's nothing we can recommend for Docker Desktop on WSL, which unfortunately is the primary setup newcomers will try this with. So changing the default to be a volume should address that (presumably by hosting the volume within the WSL Docker VM, as opposed to the host NTFS filesystem)
The text was updated successfully, but these errors were encountered: