I am running into this issue
<https://github.com/mitchellh/vagrant/issues/5186> now after packaging a
box (I'm using Vagrant 1.7.2).
Before packaging the box, everything was working fine. Then I discarded the
original VM and pointed my Vagrantfile at the resulting from the package
command.
PS C:\workspace\content_vagrant> vagrant ssh-config
Host default
HostName 127.0.0.1
User vagrant
Port 2222
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
PasswordAuthentication no
IdentityFile C:/Users/ADMIN/.vagrant.d/insecure_private_key
IdentitiesOnly yes
LogLevel FATAL
I didn't mess with anything inside the VM before packaging it so I'm not
sure what the issue could be.
After getting all the
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
messages I tried deleting the file insecure_private_key since that was one
of the suggestions. But actually the suggested workarounds seem to be all
over the place and include reinstalling Vagrant from scratch. Does anyone
know a definitive workaround to this issue?
One thing I just thought of though: I started with: the centos7 base box
--> packaged box1 --> packaged box2
It was this packaged box2 that I'm having issues with. Not sure if I would
have the same issues if I went back to packaged box1 or the base box.
Thanks
--
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
