Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VirtualBox backend should not assume same IP #583

Closed
3noch opened this issue Jan 12, 2017 · 1 comment
Closed

VirtualBox backend should not assume same IP #583

3noch opened this issue Jan 12, 2017 · 1 comment

Comments

@3noch
Copy link

3noch commented Jan 12, 2017

I often run into an issue where NixOps deploys a VirtualBox machine and saves its IP to my ~/.ssh/known_hosts file. Later on, after I've rebooted the VM, NixOps can't detect that the IP of the VM has changed and just hangs. If I remove the entry in ~/.ssh/known_hosts it seems NixOps is able to figure things out and work correctly. This problem is even worse when I deploy machines from various projects, but some deployment steals the IP from a previous deployment. In this case NixOps actually tries to connect to a running VM but it has the wrong keys.

Can we teach the VirtualBox backend not to assume the IP is the same? Also it would be nice if it could automatically remove or update ~/.ssh/known_hosts in these cases.

@domenkozar
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants