Expected behavior The MariaDB/Percona instance should be able to import an arbitrarily large DB dump file successfully. Actual behavior The MariaDB/Percona import hangs, taking the container and all communications with Docker down with them. Information Starting a MariaDB or Percona container with…

I’m also experiencing this. Any ideas how to import the sql?

I haven’t been able to find a workaround. Ultimately had to give up on storing the DB data on the host system and instead let the container manage its own storage. Not optimal from my perspective, but at least it works.

I’m also experiencing this. Only happens when trying to store data in a volume, and appears to be when importing a large table, though that may just be coincidence. I’d love to hear if someone has a solution.

An example dataset that reproduces this issue would be extremely useful in helping us to fix it. Is there any way you could share your data set or easily create one (or share a script to create one) that causes this problem? We’d really like to resolve this issue but don’t have the human bandwidth t…

Thank you for the reply, David. I can provide a dataset. I also noticed that if I do the import without using volumes, it completes in the expected amount of time. If I then attempt to cp the files out of the container to the host, the larger innodb files (>~2GB) copy very slowly, around 2 to 3MB/s…

As discussed in File access in mounted volumes extremely slow, CPU bound , I’d still really appreciate a reproduction. One which generates a representative database from a script so we don’t have to transfer gigs over the net would be lovely. In particular, with large sequential reads of large blocks…

Solved! I copied the “dump.sql” file into the container and then imported it. docker cp dump.sql CONTAINER_ID:/root/dump.sql docker exec -it CONTAINER_ID bash then inside the container: cd /root mysql -u USER -p DATABASE and then inside myqsl bash: SOURCE dump.sql;

Nice! Unfortunately more of a workaround than a fix though. I don’t want to have to copy my DB dump into the container each time I want to do an import though.

I had a similar issue, and tried this workaround, but docker crashed during big dump file copy. Then I left the file in a shared volume, launched mysql importation inside the container, and it worked: Inside the container cd /shared_volume_where_the_dump_is mysql -u USER -p DATABASE SOURCE dump.…

Docker Mac hard-locked during mariadb/percona db import

Docker Desktop

bckieffer (Bckieffer) August 5, 2016, 4:55pm 7

It appears this issue is related to file transfer speed, which has already been discussed here: File access in mounted volumes extremely slow, CPU bound

Topic		Replies	Views
Hang on postgres data import with mounted volumes Docker Desktop beta	2	9127	June 3, 2016
Incredibly slow to create tables in MySQL Docker Desktop	4	7435	December 6, 2016
Slow mysql import on windows Docker Desktop windows	9	5850	October 14, 2016
MySQL Slow Performance In Docker General	25	85060	June 2, 2022
Performance is much slower than vmware fusion based docker machine Docker Desktop	4	3972	April 27, 2016

Docker Mac hard-locked during mariadb/percona db import

Related topics