-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Hyper-V: SMB share failed to be created #12639
Comments
To add, the UAC stuff also seems to have an influence in this... so this is related to #10628 too. |
Anyone? |
anyone v2? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Vagrant version
2.2.19
Host operating system
Windows 10 10.0.19044.1415
Guest operating system
Ubuntu 20.04. But I think it does not matter, as this code is host specific.
Vagrantfile
The full Vagrantfile is at https://github.com/rgl/ubuntu-vagrant/blob/master/example/Vagrantfile.
Debug output
The relevant part is:
Expected behavior
The SMB share should have been created without any error.
Actual behavior
It failed to create the SMB with an unknown error.
After decoding the logged script from above, this comes down to:
Which , when manually executed, returns this:
Looking at that set_share.ps1 script, I have a couple of questions:
net share
instead of theNew-SmbShare
cmdlet (which is supported from Windows 2012R2+)?net share
withNew-SmbShare
worked for me.Everyone
instead of thesmb_username
given in theVagrantfile
?for
loop. It should use the-lt
(less than) operator instead of-le
(less than or equal).WARNING: empty path argument encountered - complete
message.Would a PR be acceptable for fixing this (at least 1 and 3)?
The text was updated successfully, but these errors were encountered: