hashicorp / hashicorp/vagrant

SMB Mount error: Unable to find suitable address

Open
#9,652 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

host/windows synced-folders/smb
Dominant language
Ruby
Stars
27.2k
Forks
4.4k
Avg merge
1m
Merged PRs (30d)
1

Description

### Vagrant version
2.0.3

### Virtual Box Version
5.2.8 r121009

### SMB Version
SMB Version 3

### Host operating system
Windows 10 build 16299

### Guest operating system
ubuntu 16.04

### Vagrantfile
```ruby
config.vm.synced_folder HOST_FOLDER_SF, GUEST_FOLDER_SF, :owner=> 'vagrant', :group=>'www-data', type:'smb', mount_options: ['vers=3.0']
```

### Debug output
https://gist.github.com/anrizal/d59006dd99444ae68e0cf252751c3dff

### Expected behavior
The shared folder supposed to be mounted

### Actual behavior
Sometime I found the following error.

The error output from the last command was:
Unable to find suitable address.

### Note
- command line is run with administrator privilege
- This happens often, but not always. If it happens, the only method (that I know) to fix this is to restart the computer or vagrant destroy the image.
- it is always happen if I have my VPN up
- maybe the issue is related with https://github.com/hashicorp/vagrant/issues/9540 and https://github.com/hashicorp/vagrant/issues/9660

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Vagrantfile SMB synced-folder configuration and the linked debug output, then compare the related issues #9540 and #9660. Done means identifying why address lookup fails, especially with the VPN enabled, and making the shared folder mount reliably without requiring a restart or destroy.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.