With VMware Fusion, it loads as fast as it does running natively on OS X. I don’t have any sort of metrics to provide at the moment, but the use case we’re using to test this is loading our company’s Rails application in development mode with the entire app mounted into the container as a volume. Docker Machine backed by VirtualBox had the same problem for my team, but Docker Machine backed by VMware Fusion did not. Notice the time is 0.19 seconds with no measurable CPU spike. For just over 7MB of data! Now cd / and run the same command. Notice the time is ~15 seconds, and during the operation the CPU usage of the docker process is 100%.Write a few MB of data to a file on the volume, time it:.Get on the commandline of a lightweight docker container, and mount a volume:ĭocker run -rm -it -v `pwd`:`pwd` -w `pwd` alpine /bin/sh.Executing common JS build tools like eslint, babel, and istanbul take an infeasibly long time compared to how quickly it ran using docker-machine over VirtualBox. The impact is that my team’s testing workflow involves, rather than building a new container via docker-compose for testing, simply running the node:4 container and mounting the current working directory as a volume and running tests. See steps to reproduce for the simplest use case. Information OS X: version 10.11.4 (build: 15E65)ĭocker logs are being collected into /tmp/. Actual behaviorįile access in volumes is many times slower than on non-volumes. (Submitted this via email, but since reports are happening on the forum now, I’m sharing here as well!) Expected behaviorįile access in volumes should be comparable to access times in non-volumes, similarly to Linux installations of docker, or docker on mac via docker-machine and VirtualBox.
0 kommentar(er)
