Docker Qcow2 Vs Raw Download Or Create

It allows developers to work on different projects with different technical stacks, and switch projects in a matter of seconds, as well as running two or more project at the same time.

As our company was staffing its employees with Apple laptops, we had to fix this.

Here is the story of the different tips and tricks we used in order to work efficiently with Docker for Mac.

The performances werent very good and we werent achieving native linux perfs but it was quite acceptable.

Unfortunately we faced a BIG issue with filesystem bind mount.

As we mainly work with PHP projects, especially Symfony or Magento ones, with tens of thousands of PHP files, we were devastated because of the very poor performances.

This tool synchronise your host workspace with a docker volume.

It worked quite well, we reached native linux performances, but there were some drawbacks.

It can be very frustrating if you dont figure it out quickly.

Docker volumes have native linux performances on writing which implies that our apps reached very good performances with this configuration.

Because they are annoyed by another famous Docker for Mac issue.

The Docker VM image file ( LibraryContainerscom.docker.dockerDatacom.docker.driver.amd64-linuxDocker.qcow2 ) grows continuously and can reach up to 60Gb of disk space.

Docker Qcow2 Vs Raw Download Or Create

The drawback is that you loose all your docker images (and your docker volumes), and have to download or create them again.

Does it suffer from the same space problem We havent tested it entierly right now, and in its lastest version, Docker rolled back the raw format to qcow2 because of some instabilities.

You can read the post for explanations; in short it removes checks on database writes and speed up it greatly.

It can be done on dev environnement; to do so, run-in this gist.

Magento performance are good, only PhpStorm is a bit laggy after some heavy change on directories files.

Docker For Mac Qcow2 Vs Raw