Skip to content
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.

vmware fusion machine loses keys when stopped/restarted #532

Closed
ehazlett opened this issue Feb 12, 2015 · 5 comments
Closed

vmware fusion machine loses keys when stopped/restarted #532

ehazlett opened this issue Feb 12, 2015 · 5 comments

Comments

@ehazlett
Copy link
Contributor

When stopping a VMware fusion machine the docker daemon is no longer accessible nor is ssh etc.

@ehazlett
Copy link
Contributor Author

@frapposelli ^

@frapposelli
Copy link
Contributor

Yes, I'm aware of this, it's part of the whole "seeding disk" problem, directly related to #430

Working hard on these this week 😄

@ehazlett
Copy link
Contributor Author

awesome, thanks!

@frapposelli
Copy link
Contributor

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

@ehazlett ehazlett added this to the 0.2.0 milestone Feb 26, 2015
@ehazlett ehazlett modified the milestone: 0.2.0 Mar 17, 2015
@pdevine
Copy link

pdevine commented Mar 24, 2015

I run in to the same problem. If a vm gets powered off (either through machine, a reboot, etc.), it's no longer possible to ssh into the machine and things like "docker ps" start failing. I'm using the 0.1.0 release.

tomeon pushed a commit to tomeon/machine that referenced this issue May 9, 2018
Fix a few minor issues with the Dockerfile (both for buildability and cacheability)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants