vagrant/plugins/providers/docker
Dan Carley 7529b66ea2 Disable insert_key for boot2docker host
Vagrant >1.7 is unable to login to the default boot2docker host if it has
been halted and brought back up again.

This is because the insecure SSH keypair is replaced but boot2docker doesn't
persist filesystem changes between reboots. So when next brought up Vagrant
tries to use the new keypair which is no longer valid and subsequently isn't
able to login.

Prevent this from happening by disabling the `ssh.insert_key` option on
versions where it is available.
2015-01-08 11:23:37 +00:00
..
action Use .key? instead of .has_key? 2015-01-05 18:29:01 -05:00
cap commands/rsync: handle proxy machines [GH-4066] 2014-10-22 16:17:39 -07:00
command providers/docker: check proper state for docker-logs [GH-3990] 2014-10-22 11:20:00 -07:00
executor Change symbols inside hashes to 1.9 JSON-like syntax 2014-05-22 12:35:12 -04:00
hostmachine Disable insert_key for boot2docker host 2015-01-08 11:23:37 +00:00
action.rb providers/docker: set preparing set to avoid data dir clear [GH-3873] 2014-10-22 20:52:08 -07:00
communicator.rb providers/docker: fix support of agent forwarding 2014-12-07 11:02:50 +01:00
config.rb providers/docker: support auth [GH-4042] 2014-10-22 13:12:31 -07:00
driver.rb providers/docker: build output [GH-3739] 2014-10-23 15:03:09 -07:00
errors.rb providers/docker: nicer error if package is called [GH-4595] 2014-10-21 17:04:46 -07:00
plugin.rb commands/rsync: handle proxy machines [GH-4066] 2014-10-22 16:17:39 -07:00
provider.rb providers/docker: set preparing set to avoid data dir clear [GH-3873] 2014-10-22 20:52:08 -07:00
synced_folder.rb providers/docker: support building Dockerfiles 2014-04-21 13:55:54 -07:00