sme*_*eeb 10 macos vagrant docker
更新:我已经卸载了Vagrant和Docker,并且会接受任何帮助我以下述方式重新安装它们的答案:
如果你看一下流浪的源代码,你会发现我的错误来自这行代码,这对于VirtualBox的供应商,来自该usable方法引发错误.usable如果该方法认为VirtualBox具有无效版本(VirtualBoxInvalidVersion)或未在本地系统(VirtualBoxNotDetected)上检测到它,则会引发错误.
不是Ruby开发者,现在我很难弄清楚Vagrant如何决定抛出这两个错误中的任何一个.但我想我已经越来越清楚为什么Docker正在使用我的Vagrant/VirtualBox配置.
原始问题:
Mac在这里.几天前我安装了Vagrant和VirtualBox,如下所示:
brew cask install virtualbox
brew cask install vagrant
brew cask install vagrant-manager
Run Code Online (Sandbox Code Playgroud)
......这让Vagrant起来并没有任何问题.我能够vagrant init hashicorp/precise32; vagrant up和一切看起来都运行完美(hashicorp/precise32默认情况下使用VirtualBox).
然后昨晚我安装了Docker,它也需要VirtualBox,并且运行起来没有任何问题.我甚至能够让whalesay容器示例正常工作.到现在为止还挺好.
今天我去Vagrant玩游戏,看起来我的Docker安装了我的Vagrant/VirtualBox配置.
现在,当我vagrant init hashicorp/precise32在一个空目录上运行然后运行时vagrant up,我得到:
myuser@mymac:~/sandbox/myapp$vagrant up
No usable default provider could be found for your system.
Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.
The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.
If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.
Run Code Online (Sandbox Code Playgroud)
那么我尝试指定提供者类型,即使我不应该,只是为了看看会发生什么:
myuser@mymac:~/sandbox/myapp$vagrant up --provider=VirtualBox
The provider 'VirtualBox' could not be found, but was requested to
back the machine 'cortex'. Please use a provider that exists.
Run Code Online (Sandbox Code Playgroud)
只是为了好的衡量,运行vagrant -v产生Vagrant 1.7.2输出.
什么问题出了什么问题,修复是什么?
我得到了这个工作,但不知道实际的解决方案是什么。
brew/cask)Vagrantfile来确认您的 Vagrant-Docker-VirtualBox 都能很好地协同工作| 归档时间: |
|
| 查看次数: |
1341 次 |
| 最近记录: |