Re: [vagrant-up] vagrant ssh "Permission denied" after install the 'vagrant-vbguest' plugin

[Alvaro Miranda Aguilera]

if the box you are using doesn't came with virtualbox additions thats how the person who created the box decided the experience to be.

I will suggest try different boxes until you find one that works out of the box, or create your own custom one.

Alvaro

On Wed, Apr 12, 2017 at 11:08 PM, Joe Li <krqt...@gmail.com> wrote:

Vagrant 1.9.1

box version: debian/jessie64 (virtualbox, 8.7.0)

virtualbox version: Version 5.1.14 r112924

This happens when I use customized synced folder. See the Vagrantfile below.

The synced folder wasn't working (mount: unknown filesystem type 'vboxsf') unless I install the vagrant-vbguest plugin.

After executing 'vagrant plugin install vagrant-vbguest', I cannot 'vagrant ssh' anymore.

It reports "Permission denied (Public key)".

However I can 'ssh -p 2222 vag...@127.0.0.1'.

Why is this happening and how to fix it?

# -*- mode: ruby -*-

# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure

# configures the configuration version (we support older styles for

# backwards compatibility). Please don't change it unless you know what

# you're doing.

Vagrant.configure(2) do |config|

  # The most common configuration options are documented and commented below.

  # For a complete reference, please see the online documentation at

  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for

  # boxes at https://atlas.hashicorp.com/search.

  config.vm.box = "debian/jessie64"

  # Disable automatic box update checking. If you disable this, then

  # boxes will only be checked for updates when the user runs

  # `vagrant box outdated`. This is not recommended.

  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port

  # within the machine from a port on the host machine. In the example below,

  # accessing "localhost:8080" will access port 80 on the guest machine.

  # config.vm.network "forwarded_port", guest: 80, host: 8080

  config.vm.network "forwarded_port", guest: 80, host: 1757

  # Create a private network, which allows host-only access to the machine

  # using a specific IP.

  # config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.

  # Bridged networks make the machine appear as another physical device on

  # your network.

  # config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is

  # the path on the host to the actual folder. The second argument is

  # the path on the guest to mount the folder. And the optional third

  # argument is a set of non-required options.

  config.vm.synced_folder ".", "/vagrant", disabled: true

  config.vm.synced_folder "ikiwiki/", "/home/vagrant"

  # Provider-specific configuration so you can fine-tune various

  # backing providers for Vagrant. These expose provider-specific options.

  # Example for VirtualBox:

  #

  # config.vm.provider "virtualbox" do |vb|

  #   # Display the VirtualBox GUI when booting the machine

  #   vb.gui = true

  #

  #   # Customize the amount of memory on the VM:

  #   vb.memory = "1024"

  # end

  #

  # View the documentation for the provider you are using for more

  # information on available options.

  # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies

  # such as FTP and Heroku are also available. See the documentation at

  # https://docs.vagrantup.com/v2/push/atlas.html for more information.

  # config.push.define "atlas" do |push|

  #   push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"

  # end

  # Enable provisioning with a shell script. Additional provisioners such as

  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the

  # documentation for more information about their specific syntax and use.

  # config.vm.provision "shell", path: "provision.sh"

end

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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 vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/c517102d-4ff2-4c17-92af-f43e44b164c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro