Vagrant WSL rsync and ssh permission error -
i have strange problem, although self-explaining, keep having permission problems when using rsync , vagrant ssh in wsl.
i have vagrant version 1.9.8 installed in windows in wsl. exported following environment variables:
export vagrant_wsl_enable_windows_access="1" export vagrant_wsl_windows_access_user_home_path="/mnt/c/vagrant" when run vagrant up succesfully creates vm in virtualbox. halfway following error:
==> salt: rsyncing folder: /mnt/c/vagrant/ => /vagrant there error when attempting rsync synced folder. please inspect error message below more info. host path: /mnt/c/vagrant/ guest path: /vagrant command: "rsync" "--verbose" "--archive" "--delete" "-z" "--copy-links" "--no-owner" "--no-group" "--rsync-path" "sudo rsync" "-e" "ssh -p 2222 -o loglevel=fatal -o controlmaster=auto -o controlpath=/tmp/ssh.216 -o controlpersist=10m -o identitiesonly=yes -o stricthostkeychecking=no -o userknownhostsfile=/dev/null -i '/mnt/c/vagrant/.vagrant.d/insecure_private_key'" "--exclude" ".vagrant/" "/mnt/c/vagrant/" "vagrant@127.0.0.1:/vagrant" error: permission denied (publickey,gssapi-keyex,gssapi-with-mic). rsync: connection unexpectedly closed (0 bytes received far) [sender] rsync error: unexplained error (code 255) @ io.c(226) [sender=3.1.0] when use vagrant ssh salt error:
permission denied (publickey,gssapi-keyex,gssapi-with-mic). it doesn't matter kind of vagrantfile use. when place vagrantfile in /root of wsl, can use vagrant ssh, still error of rsync.
this strange because wsl documentation of vagrant saying following:
other useful wsl related environment variables: vagrant_wsl_windows_access_user - override current windows username vagrant_wsl_disable_vagrant_home - not modify vagrant_home variable vagrant_wsl_windows_access_user_home_path - custom windows system home path if vagrant project directory not within user's home directory on windows system, actions include permission checks may fail (like vagrant ssh). when accessing vagrant projects outside wsl vagrant skip these permission checks when project path within path defined in vagrant_wsl_windows_access_user_home_path environment variable. example, if user wants run vagrant project wsl located @ c:\testdir\vagrant-project: does know how solve problem? or has experienced problem himself? hope can me out.
for people interested in this, here solution (at least solution me).
i deleted vagrant_wsl_windows_access_user_home_path="/mnt/c/vagrant" environment variable. noticed vagrant_home environment variable not set. when set default location (~/.vagrant.d) can work , manipulate file permissions, can't windows files.
so use this:
$ export vagrant_home="/home/<user>/.vagrant.d" after changing key rsync problem gone, ssh permission error still there. because vagrant inserting new ssh key default , places in .vagrant folder in root directory of vagrantfile. make sure putting in vagrantfile:
config.ssh.insert_key = false the main cause of problem vagrant permission check on ssh keys. since vagrant put new generated ssh key in same folder vagrantfile, fail due permission checks. permission check fail on windows path. setting config.ssh.insert_key = false keep default insecure key, located in vagrant_home folder.
i experienced problems config file in .ssh folder. git ssh configuration used rsaauthentication yes option. therefor rsync can fail also.
i hope struggling wsl well. have working vagrant setup in wsl on windows.
Comments
Post a Comment