I guess I forgot about this thread. I've just added an 
issue: https://github.com/hashicorp/vagrant/issues/10274

On Saturday, February 24, 2018 at 5:59:57 AM UTC-5, Alvaro Miranda Aguilera 
wrote:
>
> developers saw your message and they are thinking
>
> feel free to open an issue on github
>
>
> On Fri, Feb 23, 2018 at 12:36 AM, Jamie Jackson <[email protected] 
> <javascript:>> wrote:
>
>> That diff was messed up, it should have been:
>>
>> -          if v.include?(":") && @executor.windows?
>>
>> +          if false && v.include?(":") && @executor.windows?
>>
>> On Wednesday, February 21, 2018 at 7:31:36 PM UTC-5, Jamie Jackson wrote:
>>>
>>> Vagrant seems to be trying to manipulate my local path, for some reason:
>>>
>>> Vagrantfile snippet:
>>>
>>>   config.vm.define "centos-jenkins" do |c|
>>>     c.vm.provider "docker" do |d|
>>>       d.name = "centos-jenkins2"
>>>       d.image = "jenkins/jenkins:2.91-alpine"
>>>       d.ports  = ["9898:8080"]
>>>       d.volumes = 
>>> ['/c/Users/15037/workspace/centos-vagrant-fresh:/var/jenkins_home']
>>>     end
>>>   end
>>>
>>>
>>> Output:
>>>
>>>
>>> Command: ["docker", "run", "--name", "centos-jenkins2", "-d", "-p", 
>>> "9898:8080", "-v", 
>>> "c\\Users\\15037\\workspace\\centos-vagrant-fresh:/var/jenkins_home", 
>>> "jenkins/jenkins:2.91-alpine", {:notify=>[:stdou
>>> t, :stderr]}]
>>>
>>> Stderr: C:\Program Files\Docker Toolbox/docker.EXE: Error response from 
>>> daemon: create c\Users\15037\workspace\centos-vagrant-fresh: 
>>> "c\\Users\\15037\\workspace\\centos-vagrant-fresh" includes invalid 
>>> characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are 
>>> allowed. If you intended to pass a host directory, use absolute path.
>>> See 'C:\Program Files\Docker Toolbox/docker.EXE run --help'.
>>>
>>>
>>> How can I get it to leave my path alone? (It works fine from a straight 
>>> `docker run`.)
>>>
>>>
>>> -- 
>> 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 [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/1581532e-fb3d-4ce7-9d85-138330955503%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/vagrant-up/1581532e-fb3d-4ce7-9d85-138330955503%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Alvaro
>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/b170229e-9f62-47ae-8923-f9e8b4d12270%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to