You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:
Unable to resolve dependency: 'vagrant-triggers (= 0.5.3)' requires 'bundler (~> 1.3)'
In debug log:
DEBUG bundler: Current source list for install: ["file://d/install/", "https://rubygems.org/", "https://gems.hashicorp.com/"]
This URL is correct?
Exist any workaround (another than downgrade to version 1.7.4)?
The text was updated successfully, but these errors were encountered:
D:\Install>vagrant plugin install specs.4.8 --plugin-source file://d:/install/ --plugin-version 4.8
Installing the 'specs.4.8 --version '4.8'' plugin. This can take a few minutes...
Vagrant failed to load a configured plugin source. This can be caused
by a variety of issues including: transient connectivity issues, proxy
filtering rejecting access to a configured plugin source, or a configured
plugin source not responding correctly. Please review the error message
below to help resolve the issue:
Errno::ETIMEDOUT: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. - connect(2) for "api.rubygems.org" port 443 (https://api.rubygems.org/specs.4.8.gz)
Source: https://rubygems.org/
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 2, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Vagrant version
Vagrant 1.9.3
Host operating system
Microsoft Windows 10 Pro 10.0.10240
Guest operating system
Guest no needed
Vagrantfile
Vagrantfile no needed
Debug output
reproduce step 3
reproduce step 4
reproduce step 5
Expected behavior
Plugin installed successful.
Actual behavior
Plugin not installed
Steps to reproduce
vagrant plugin install vagrant-triggers-0.5.3.gem
fetch_path': undefined method
fetch_d'OK, maybe im using wrong URI?
vagrant plugin install file://D:/Install/vagrant-triggers-0.5.3.gem
`initialize': Invalid argument @ rb_sysopen - D:/Install/file:/D:/Install/vagrant-triggers-0.5.3.gem
(Errno::EINVAL)
Interesting file path...
vagrant plugin install vagrant-triggers --plugin-source file://d:/install/ --plugin-version 0.5.3
In debug log:
DEBUG bundler: Current source list for install: ["file://d/install/", "https://rubygems.org/", "https://gems.hashicorp.com/"]
This URL is correct?
Exist any workaround (another than downgrade to version 1.7.4)?
The text was updated successfully, but these errors were encountered: