vmwareFusion 'stop' too harsh

[leth]

After a stop/start the Docker daemon fails to start due to empty trust file.

The process I followed is roughly this:

• docker-machine create -d vmwarefusion --vmwarefusion-boot2docker-url https://github.com/cloudnativeapps/boot2docker/releases/download/v1.4.1-vmw/boot2docker-1.4.1-vmw.iso boot2docker
• docker pull busybox
• docker-machine stop
• docker-machine start
• docker ps (fails, VM daemon never starts)

Looking into the logs, the file at /var/lib/docker/trust/official.json was empty, and docker failed when parsing it.

Manually running sync in the VM after pulling busybox allowed the daemon to start okay later, so it looks like what is needed is a more graceful stop implementation.

[frapposelli]

Good call, putting boot2docker/boot2docker#638 to reference the need to appropriately run shutdown through OVT.

[ehazlett]

I have a PR to use your custom ISO for the time being. Once that is merged
we should have everything in the custom ISO to do this correct?

On Sun, Feb 8, 2015 at 9:47 PM, Fabio Rapposelli notifications@github.com
wrote:

Good call, putting boot2docker/boot2docker#638
boot2docker/boot2docker#638 to reference the
need to appropriately run shutdown through OVT.

—
Reply to this email directly or view it on GitHub
#507 (comment).

[frapposelli]

@ehazlett I need to double check that, I'm not 100% sure.

[ehazlett]

Thanks

On Monday, February 9, 2015, Fabio Rapposelli notifications@github.com
wrote:

@ehazlett https://github.com/ehazlett I need to double check that, I'm
not 100% sure.

—
Reply to this email directly or view it on GitHub
#507 (comment).

[leth]

Are you certain you need the guest tools for this? Perhaps there is an API call to simulate the power button being pressed?

[frapposelli]

As a reference, this issue depends on boot2docker/boot2docker#747

This PR effectively replace all the other VMware PRs for Boot2Docker.