mysql data lost after docker rm -f $(docker ps -a -q) about launchpad HOT 6 CLOSED

Hello, definitely not a bug ;-)

Saving MySQL data on the Host would be a very bad approach.
You can do it of course. That is just docker configuration in the docker-compose. (see Docker doc)

I would recommend to use ez dumpdata and to reimport ez importdata those commands would dump and import an archive on your filesystem (host). It allows you to save your databases before to remove the container.

from launchpad.

from launchpad.

Ibexa(eZ)told you not to use eZ Launchpad?
Interesting, I would love to know why, can we know more?

The 30Go situation is indeed an information that will have been good to have in the issue ;)

I think it is still bad to put mysql data on the host. I would use a Docker Named Volume for that.

But that's not related to eZ Launchpad really. You can do all the customizations you want in your docker-compose file in provisioning/dev. As well as using the host to store mysql data if you really want to.

from launchpad.

from launchpad.

It is bad because:

• it is not docker thinking
• on Mac OS performance are catastrophic (this is why we are using NFS mount point with Launchpad for the code). Read/Write on the Host from within a container is slow with Docker For Mac: really slow. So I guess writing cache needs more than write MySQL but still.

You wrote that eZ told you not to use Launchpad, can we know more here. That's something important for future reader off this issue and we/you need to make thing clear ;-)

Thank you

from launchpad.

from launchpad.