-
Notifications
You must be signed in to change notification settings - Fork 286
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
Docker Desktop for Windows 2.2 breaks MariaDB #5604
Comments
I have the same error.
|
Could you try again with the new version 2.2.0.3? We have fixed several bugs related to file sharing. Thank you. |
Updated to latest version 2.2.0.3 and the problem is still here. version: '3.3'
services:
mariadb:
image: mariadb:10.4
restart: 'no'
environment:
MYSQL_DATABASE: random
MYSQL_USER: test
MYSQL_PASSWORD: test
MYSQL_ROOT_PASSWORD: test
ports:
- '13333:3306'
volumes:
- './data:/var/lib/mysql'
command:
'mysqld --innodb-flush-method=fsync --innodb-use-native-aio=0'
First time starting the container I get this output:
Only the errors:
|
Tried it on my home PC too. Both are Windows 10 18363. Just start the container (docker-compose file above). Create a table, fill it with some data. Duplicate the table and truncate the copy. Or rename the table.
Full log
|
I had the same error like @djereg . My version of Docker was 2.2.0.3. I downgrade to 19.03.5 and everything work good. |
Thanks for your report. I think the current Windows volume sharing code does not handle reliably the case where an open file is being renamed. This bug is on our backlog. Having said that, performance will be much better if you use a persistent Docker volume for the database, rather than remote the database to the host. For example:
The volume |
I can reproduce this error while running this:
But it works fine with MariaDB (10.3.22-MariaDB - Debian 10) and with MySQL (8.0.19, latest Docker) - why not, that isn't special. |
The latest release (2.2.0.4) resolved my issues; I am able to restructure tables without crashing mariadb. I was hopeful, as the release notes mentions many bug fixes around file share between docker container and windows host, specifically around Open files. BTW, I've been struggling with this issue since I upgraded to 2.2.0.3 (I don't recall what version I had before). |
I had a similar issue caused by some specific table name (WordPress site database with WordFence) and I was able to fix this using the extra option
Edit: When import of the sql dump to a mysql server on a *nix server doesn't work, use |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
Docker for MariaDB boots.
Actual behavior
MariaDB fails to boot.
Information
Steps to reproduce the behavior
This has worked with the previous version of Docker Desktop. Now it doesn't, with the following error.
If I remove the
volume
mounting, it starts working.So what's going wrong here and what did 2.2 break?
The text was updated successfully, but these errors were encountered: