-
Notifications
You must be signed in to change notification settings - Fork 106
Mkdir error when trying resync after restarting docker machine with vmware driver #178
Comments
Hm, I'm not sure docker-osx-dev has been tested with anything other than Virtualbox. In fact, docker-osx-dev exists specifically to work around the shortcomings of vboxsf, which is horrendously slow. If you're not using Virtualbox, do you really need docker-osx-dev? |
@brikis98 vmware shares suffer from the same performance problems docker-osx-dev is designed to overcome with Virtualbox. Now that I am using docker-osx-dev (with virtualbox driver at the moment), development with docker is actually productive! Vmware has performed better than virtualbox for me, so those of us who prefer vmware would benefit from docker-osx-dev support for it through docker machine. Seems like an absent filesystem problem going on with busybox on vmware fusion. |
Ah, I didn't realize vmware had the same issue. Could you run docker-osx-dev with debug logging and post the full output here? |
Good feedback @snipebin, thanks. I remember I didn't even get my volumes working with VMWare, they were all corrupt, so I didn't trial it further. |
@brikis98 here is the debug output, starting after fresh machine creation following steps 1-5 above:
After
|
How odd. The |
My 2 cents: VMWare driver has had problems, e.g. docker/machine#2050 and docker/machine#1789 I experienced myself and I'm seeing some overlap here in this ticket. |
@brikis98 here's output from df and mount:
I am running docker-machine with
This was interesting, trying to create
while
@ain Thanks for the references. |
To reproduce:
docker-machine create -d vmwarefusion test-machine
eval "$(docker-machine env test-machine)"
docker-osx-dev install
docker-osx-dev
docker-machine restart test-machine
docker-osx-dev
You should see:
Update:
This does not happen with the Virtualbox driver.
Here are the env variables used in the creation of the machines:
export FUSION_CPU_COUNT=-1 export VIRTUALBOX_CPU_COUNT=2 export FUSION_MEMORY_SIZE=4096 export VIRTUALBOX_MEMORY_SIZE=4096 export FUSION_NO_SHARE=true export VIRTUALBOX_NO_SHARE=true
The text was updated successfully, but these errors were encountered: