sap-nw-abap-vagrant icon indicating copy to clipboard operation
sap-nw-abap-vagrant copied to clipboard

Run install_addons.sh when deployed on FAT32 formated external HDD

Open bmml1 opened this issue 5 years ago • 1 comments

Hello,

the installations works like a charm, but since FAT32 does not support file permission there seems to be a problem with accessing the private key when connecting. Copying the private key somewhere to your homefolder and then specifying the path works.

F:\Vagrant>vagrant ssh -c "sudo /vagrant/scripts/install_addons.sh" [email protected]: Permission denied (publickey).

ssh -i c:\users\<user>\.ssh\private_key_vagrant [email protected] -p 2222

bmml1 avatar Jul 27 '19 11:07 bmml1

hmm, this is not an issue of vagrant or config. this is default behavior of ssh. Not sure if there is an easy solution. Made a short search, potentially these 2 articles are of interest:

  • https://shakedos.com/passing-vagrant-command-line-parameters
  • https://ermaker.github.io/blog/2015/11/18/change-insecure-key-to-my-own-key-on-vagrant.html
  • and maybe partially this one https://github.com/hashicorp/vagrant/issues/8058

So

  • e.g. there can be a parameter e.g. --ssh-key
  • if it is specified, then Vagrant can be blocked from creating a random key
  if argSshKey
    config.ssh.private_key_path = [argSshKey, "~/.vagrant.d/insecure_private_key"]
    config.ssh.insert_key = false
  end
  • but then there is a problem to add authorized key into the machine. either it needs additional param to specify the public key too, or it should generate it from private.Heap of params is ugly. Whereas the private one is not accessible from VM. And the host might not have ssh-gen ... no elegant solution at the first glance :(

What do you think ?

sbcgua avatar Jul 29 '19 18:07 sbcgua