Skip to content
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

Unable to install vagrant-windows on vagrant 1.8.6 #203

Closed
vinyar opened this issue Nov 3, 2016 · 4 comments
Closed

Unable to install vagrant-windows on vagrant 1.8.6 #203

vinyar opened this issue Nov 3, 2016 · 4 comments

Comments

@vinyar
Copy link

vinyar commented Nov 3, 2016

It seems very odd that I'd be the first one here reporting this issue, so it's likely that I'm doing something wrong.

ENV:

$ vagrant -v
Vagrant 1.8.6
$ vagrant plugin list
vagrant-share (1.1.5, system)
$ chef -v  [ruby-2.0.0p648]
Chef Development Kit Version: 0.18.30
chef-client version: 12.14.89
delivery version: master (d86679335580be3de22996ef294b20d525889d8d)
berks version: 5.1.0
kitchen version: 1.13.2
vagrant plugin install vagrant-windows
Installing the 'vagrant-windows' plugin. This can take a few minutes...
The plugin(s) can't be installed due to the version conflicts below.
This means that the plugins depend on a library version that conflicts
with other plugins or Vagrant itself, creating an impossible situation
where Vagrant wouldn't be able to load the plugins.

You can fix the issue by either removing a conflicting plugin or
by contacting a plugin author to see if they can address the conflict.

Vagrant could not find compatible versions for gem "vagrant":
  In Gemfile:
    vagrant (= 1.8.6)

    vagrant-windows was resolved to 0.0.1, which depends on
      vagrant (~> 1.0.3)
Vagrant could not find compatible versions for gem "winrm":
  In Gemfile:
    vagrant (= 1.8.6) was resolved to 1.8.6, which depends on
      winrm (~> 1.6)

    vagrant-windows was resolved to 1.0.0, which depends on
      winrm (~> 1.1.1)

    vagrant (= 1.8.6) was resolved to 1.8.6, which depends on
      winrm-fs (~> 0.3.0) was resolved to 0.3.2, which depends on
        winrm (~> 1.5)
@ferventcoder
Copy link
Contributor

ferventcoder commented Nov 3, 2016

Not odd - Windows support is built into Vagrant. Unless I'm mistaken this gem is deprecated.

@maxi1192
Copy link

maxi1192 commented Feb 14, 2017

the readme says for vagrant 1.6+ (I installed vagrant 1.9.1) this plugin is not needed to run windows guests, but when I want to "vargant up" a windows guest with e.g. this box "opentable/win-7-professional-amd64-nocm", it says:

vagrant-windows missing, please install the vagrant-windows plugin!
Run this command in your terminal:
vagrant plugin install vagrant-windows

@ferventcoder
Copy link
Contributor

@maxi1192 It's likely they have something in their vagrantfile that is requesting that. You may need to remove something there so that things will work.

@vinyar
Copy link
Author

vinyar commented Apr 5, 2017

yup. Confirmed that opentable boxes are broken due to busted Vagrant files baked into .box files

Vagrant.configure("2") do |config|
    config.vm.define "vagrant-windows-7"
    config.vm.box = "windows_7"

    if !Vagrant.has_plugin?('vagrant-windows')
      puts "vagrant-windows missing, please install the vagrant-windows plugin!"
      puts "Run this command in your terminal:"
      puts "vagrant plugin install vagrant-windows"
      exit 1
    end
...

@vinyar vinyar closed this as completed Apr 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants