Open fabiankrack opened 8 years ago
@onibox how were vagrant and vagrant-aws installed on this machine? I haven't tried running on FreeBSD in many months now. This error looks to me like gem
is using a different GEM_HOME
than vagrant
somehow, but that would only make sense to me if you were using RVM or something similar
@rtyler vagrant was installed via FreeBSD packages while vagrant-aws was installed as a normal user, not root. I don't use rvm nor rbenv.
fmk@~> gem environment
RubyGems Environment:
- RUBYGEMS VERSION: 2.5.1
- RUBY VERSION: 2.1.8 (2015-12-16 patchlevel 440) [amd64-freebsd10]
- INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/2.1
- USER INSTALLATION DIRECTORY: /home/fmk/.gem/ruby/2.1
- RUBY EXECUTABLE: /usr/local/bin/ruby21
- EXECUTABLE DIRECTORY: /usr/local/bin
- SPEC CACHE DIRECTORY: /home/fmk/.gem/specs
- SYSTEM CONFIGURATION DIRECTORY: /usr/local/etc
- RUBYGEMS PLATFORMS:
- ruby
- amd64-freebsd-10
- GEM PATHS:
- /usr/local/lib/ruby/gems/2.1
- /home/fmk/.gem/ruby/2.1
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :backtrace => false
- :bulk_threshold => 1000
- REMOTE SOURCES:
- https://rubygems.org/
- SHELL PATH:
- /usr/local/sbin
- /usr/local/bin
- /home/fmk/bin
- /sbin
- /bin
- /usr/sbin
- /usr/bin
- /usr/games
All ruby gems mentioned in the warning message are present with propper versions in /usr/local/lib/ruby/gems/2.1/gems and were also installed via FreeBSD packages.
fmk@~> ls /usr/local/lib/ruby/gems/2.1/gems
builder-3.2.2 listen-3.0.6 rb-inotify-0.9.7
bundler-1.11.2 little-plugger-1.1.4 rb-kqueue-0.2.4
childprocess-0.5.9 log4r-1.1.10 rest-client-1.8.0
domain_name-0.5.20160310 logging-1.8.2 ruby-termios-0.9.6
erubis-2.7.0 mime-types-2.99.1 rubyntlm-0.6.0
ffi-1.9.10 multi_json-1.11.2 rubyzip-1.2.0
gssapi-1.2.0 net-scp-1.2.1 unf-0.1.4
gyoku-1.3.1 net-sftp-2.1.2 unf_ext-0.0.7.2
hashicorp-checkpoint-0.1.4 net-ssh-3.1.1 uuidtools-2.1.5
http-cookie-1.0.2 netrc-0.7.7 vagrant-1.8.1
httpclient-2.7.1 nokogiri-1.6.7.2 wdm-0.1.0
i18n-0.7.0 nori-2.6.0 winrm-1.3.3
json_pure-1.8.3 rb-fsevent-0.9.7 winrm-fs-0.2.3
There are also gems installed in $HOME/.vagrant.d/gems/gems which seem to be even newer then the ones installed via FreeBSD packages.
fmk@~> ls $HOME/.vagrant.d/gems/gems/
CFPropertyList-2.3.2 fog-openstack-0.1.7 formatador-0.2.5
domain_name-0.5.20160615 fog-powerdns-0.1.1 httpclient-2.8.0
excon-0.50.1 fog-profitbricks-0.0.5 inflecto-0.0.2
fission-0.5.0 fog-rackspace-0.1.1 ipaddress-0.8.3
fog-1.38.0 fog-radosgw-0.0.5 mime-types-2.99.2
fog-aliyun-0.1.0 fog-riakcs-0.1.0 mini_portile2-2.1.0
fog-atmos-0.1.0 fog-sakuracloud-1.7.5 multi_json-1.12.1
fog-aws-0.9.4 fog-serverlove-0.1.2 net-ssh-3.2.0
fog-brightbox-0.10.1 fog-softlayer-1.1.2 netrc-0.11.0
fog-cloudatcost-0.1.2 fog-storm_on_demand-0.1.1 nokogiri-1.6.8
fog-core-1.40.1 fog-terremark-0.1.0 pkg-config-1.1.7
fog-dynect-0.0.3 fog-vmfusion-0.1.0 rbvmomi-1.8.2
fog-ecloud-0.3.0 fog-voxel-0.1.0 trollop-2.1.2
fog-google-0.1.0 fog-vsphere-0.8.0 vagrant-aws-0.7.0
fog-json-1.0.2 fog-xenserver-0.2.3 xml-simple-1.1.5
fog-local-0.3.0 fog-xml-0.1.2
GEM_HOME is not set.
When using vagrant-aws on FreeBSD 10.3 with vagrant 1.8.1 i get
Although i do fulfill the specs as far as i can see, e.g.