Thanks, I've switched boxes. This also *seems* to have solved the issue
where the VM would randomly spew out IO errors and become read only during
provisioning.
On Tuesday, 13 March 2018 20:11:00 UTC, Alvaro Miranda Aguilera wrote:
>
> for xenial if you want shared folder and the box doesn't hav
for xenial if you want shared folder and the box doesn't have it, use a
different box will be easier
ie
https://app.vagrantup.com/cbednarski/boxes/ubuntu-1604
On Tue, Mar 13, 2018 at 3:22 PM, 'Marcus Povey' via Vagrant <
vagrant-up@googlegroups.com> wrote:
> ... and I think this is down to va
... and I think this is down to vagrant-vbguest failing, for some reason
the guest OS is becoming readonly randomly during boot. No clue what's
going on there
On Tuesday, 13 March 2018 13:49:04 UTC, Marcus Povey wrote:
>
> Thought about this some more, and it's obvious what's going on...
>
>
Thought about this some more, and it's obvious what's going on...
authorized_keys is in /home/vagrant, so *obviously*, when I mount my
working directory over that, it becomes inaccessible. *doh*
Of course now, I'm running into a separate problem, whereby if I mount to
/vagrant, mounting doesn't
Hi, thank you for your help.
I've done a little bit of digging, as you suggested.
The problem appears to be with the synced_folder entry. Before this, I
could ssh in, if the box is provisioned with this line, SSH is no longer
possible. This with the ubuntu/xenial box, updated to latest.
If I s
Hello
Well what I said was basically start minimal and do a change as the time
start with a Vagrantfile like this:
Vagrant.configure("2") do |config|
#config.ssh.insert_key = false
#config.vm.box = "ubuntu/xenial64"
config.vm.box = "hashicorp/precise64"
#config.vm.boot_timeout = 6
Hi, thanks for getting back to me.
I tried what you said, both on my own computer and my colleague's computer.
Both cases after bringing up the box with no provisioning, vagrant ssh
failed.
Here's the Vagrantfile:
Vagrant.configure("2") do |config|
config.ssh.insert_key = false
config.
share a zip with the project or the Vagrantfile if you don' have any
provision.
I would say
1. try like this
vagrant destroy
vagrant up --no-provision
vagrant ssh
vagrant reload
works?
if yes, something is breaking this
2. try with a different box
vagrant destroy
vagrant up --no-provision
va
This is a weird one that I can't get to the bottom of...
Linux vagrant box, booted and provisioned OK.
If the box is spun up using "vagrant up", subsequent calls to "vagrant ssh"
will fail with "invalid public key". Vagrant ssh-config points to the
insecure key (correct).
I have also tried remo
