You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: