I am trying to install laravel/homestead however, during the installation I encountered an error with my VBoxManage when I ran the command vagrant up, what can I do to fix this?
Distro: openSUSE Leap 42.1
Vagrant version: 1.8.6
VirtualBox version: 5.0.26_SUSE r108824
The Error:
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["hostonlyif", "create"]
Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: Operation not permitted
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg*)" at line 71 of file VBoxManageHostonly.cpp
Does this have anything to do with permissions? because of Operation not permitted?
I checked the file with ls -l /dev/vboxnetctl and this is what it returned:
crw------- 1 root root 10, 55 Oct 3 07:24 /dev/vboxnetctl
Should I be changing the permission of this file? If so, I want to let you know that I did it before and it still shows an error, but this error is different:
/home/troopy712139/Homestead/scripts/homestead.rb:4:in `configure': undefined method `[]' for nil:NilClass (NoMethodError)
from /home/troopy712139/Homestead/Vagrantfile:30:in `block in <top (required)>'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/config/v2/loader.rb:37:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/config/v2/loader.rb:37:in `load'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/config/loader.rb:113:in `block (2 levels) in load'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/config/loader.rb:107:in `each'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/config/loader.rb:107:in `block in load'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/config/loader.rb:104:in `each'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/config/loader.rb:104:in `load'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/vagrantfile.rb:28:in `initialize'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/environment.rb:746:in `new'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/environment.rb:746:in `vagrantfile'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/environment.rb:492:in `host'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/environment.rb:214:in `block in action_runner'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:33:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:33:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/environment.rb:479:in `hook'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/environment.rb:728:in `unload'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/bin/vagrant:177:in `ensure in <main>'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/bin/vagrant:177:in `<main>'
The VBoxManage hostonlyif create command worked once when I ran it in root.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'vboxnet1' was successfully created
Can you try running sudo vagrant up --provision.
You may also want to check to make sure your paths match up in the Homestead.yaml file
So it seems all I needed to do was make vboxnetctl be owned by me, and restart my computer. I also added vboxdrv to run on startup by running this code:
service vboxdrv start
The error around: /dev/vboxnetctl tells you that your user doesn't have access there.
Try something line:
sudo usermod -a -G vboxusers
Alvaro
Related
I just installed chef-workstation on mac, I also have rvm installed on my machine. The chef-workstation is successfully installed but when I try to run chef exec command it fails with below error -
Traceback (most recent call last):
20: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/bin/ruby_executable_hooks:22:in `<main>'
19: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/bin/ruby_executable_hooks:22:in `eval'
18: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/bin/chef:23:in `<main>'
17: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/bin/chef:23:in `load'
16: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/bin/chef:25:in `<top (required)>'
15: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/cli.rb:73:in `run'
14: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/command/base.rb:58:in `run_with_default_options'
13: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/command/env.rb:39:in `run'
12: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/command/env.rb:39:in `tap'
11: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/command/env.rb:41:in `block in run'
10: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/command/env.rb:57:in `ruby_info'
9: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/command/env.rb:57:in `tap'
8: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/command/env.rb:60:in `block in ruby_info'
7: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/command/env.rb:60:in `tap'
6: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/command/env.rb:63:in `block (2 levels) in ruby_info'
5: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/command/env.rb:69:in `gem_environment'
4: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/command/env.rb:69:in `tap'
3: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/command/env.rb:70:in `block in gem_environment'
2: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/helpers.rb:124:in `omnibus_env'
1: from /Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/helpers.rb:72:in `omnibus_embedded_bin_dir'
/Users/tusharhawaldar/.rvm/gems/ruby-2.6.0#base/gems/chef-dk-3.11.3/lib/chef-dk/helpers.rb:142:in `omnibus_expand_path': Can not find omnibus installation directory for Chef. (ChefDK::OmnibusInstallNotFound)
When I checked for omnibus_root path it is giving -
/Users/tusharhawaldar/.rvm/rubies
And it is trying to find bin & /embedded/bin directories at omnibus_root_path, which are not present there, so it is raising this error.
I manually created these directories at omnibus_root_path, and I can now run the chef exec command, but when it run the chefspec it is now giving below error -
An error occurred while loading ./spec/unit/recipes/initial_packages_spec.rb.
Failure/Error: require 'chefspec'
LoadError:
cannot load such file -- chefspec
./spec/spec_helper.rb:1:in `<top (required)>'
./spec/unit/recipes/initial_packages_spec.rb:1:in `<top (required)>'
No examples found.
require 'chefspec' is failing means something missing in setup, which I doubt is related to chef omnibus.
What should be the correct way to resolve error related to ChefDK::OmnibusInstallNotFound?
Okay, so after trying various things, I finally found a solution for error -
Can not find omnibus installation directory for Chef. (ChefDK::OmnibusInstallNotFound)
And it is running below command for path update -
echo 'export PATH="/opt/chef-workstation/embedded/bin:$PATH"' >> ~/.bash_profile && source ~/.bash_profile
From - https://www.tutorialspoint.com/chef/chef_workstation_setup.htm
The Omnibus Chef will install Ruby and all the required Ruby gems into /opt/chef/embedded by adding /opt/chef/embedded/bin directory to the .bash_profile file.
trying to get started testing kubernetes with inspec using: https://github.com/bgeesaman/inspec-k8s
Im running it from the make and docker image found here: https://github.com/bgeesaman/inspec-k8s-sample
I have multiple eks clusters and a local docker-desktop cluster. When i try and connect to any of them via: inspec exec . -t k8s://docker-desktop (Matching the kubeconfig -name: xxx to the value put after k8s://) I always get the same error:
# inspec exec -t k8s://docker-desktop
Traceback (most recent call last):
20: from /usr/local/bundle/bin/inspec:23:in `<main>'
19: from /usr/local/bundle/bin/inspec:23:in `load'
18: from /usr/local/bundle/gems/inspec-bin-4.18.51/bin/inspec:11:in `<top (required)>'
17: from /usr/local/bundle/gems/inspec-4.18.51/lib/inspec/base_cli.rb:35:in `start'
16: from /usr/local/bundle/gems/thor-0.20.3/lib/thor/base.rb:466:in `start'
15: from /usr/local/bundle/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'
14: from /usr/local/bundle/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'
13: from /usr/local/bundle/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'
12: from /usr/local/bundle/gems/inspec-4.18.51/lib/inspec/cli.rb:284:in `exec'
11: from /usr/local/bundle/gems/inspec-4.18.51/lib/inspec/cli.rb:284:in `new'
10: from /usr/local/bundle/gems/inspec-4.18.51/lib/inspec/runner.rb:78:in `initialize'
9: from /usr/local/bundle/gems/inspec-4.18.51/lib/inspec/runner.rb:86:in `configure_transport'
8: from /usr/local/bundle/gems/inspec-4.18.51/lib/inspec/backend.rb:53:in `create'
7: from /usr/local/bundle/gems/train-kubernetes-0.1.6/lib/train-kubernetes/transport.rb:9:in `connection'
6: from /usr/local/bundle/gems/train-kubernetes-0.1.6/lib/train-kubernetes/transport.rb:9:in `new'
5: from /usr/local/bundle/gems/train-kubernetes-0.1.6/lib/train-kubernetes/connection.rb:13:in `initialize'
4: from /usr/local/bundle/gems/train-kubernetes-0.1.6/lib/train-kubernetes/connection.rb:36:in `parse_kubeconfig'
3: from /usr/local/bundle/gems/k8s-ruby-0.10.5/lib/k8s/client.rb:40:in `config'
2: from /usr/local/bundle/gems/k8s-ruby-0.10.5/lib/k8s/transport.rb:81:in `config'
1: from /usr/local/bundle/gems/k8s-ruby-0.10.5/lib/k8s/transport.rb:117:in `token_from_exec'
/usr/local/bundle/gems/k8s-ruby-0.10.5/lib/k8s/transport.rb:117:in ``': No such file or directory - aws (Errno::ENOENT)
I thought it was because of eks kubeconfigs being linked to the aws profile. But i get the same error for docker-desktop as well.
I tried updating the Makefile COMMAND with: COMMAND=docker run --rm -it -v pwd:$(WORKDIR) -v $(HOME)/.kube:/root/.kube:ro -v $(HOME)/.aws:/root/.aws:ro
After the error ends with No such file or directory - aws but no joy.
Any ideas how to resolve or progress?
Thanks
Small update, It did start running after making sure names where correct. But then stopped again..
I had connected to docker-desktop (It wasnt running when i orginally ran it)
I had connected to an eks cluster
I did a vi controls/basic.rb to start looking playing with my tests and it started erroring again.
I thought it might error due to a syntax problem with my changes so did a new make build but still no joy now :(
I have also tried updating the chef/inspec image to the latest 4.26 but this breaks the dockerfile as it doesnt have apk anymore.
Ok, i dont get it but i can get it to run:
It looks to be linked to im using kubectx. If i set kubectx to docker-desktop and then run the docker image it works. If im set to anything else it doesnt.
I am trying to setup Laravel homestead on a windows machine according to the documentation here: http://laravel.com/docs/5.0/homestead#installation-and-setup.
However when I get to the 'Launch The Vagrant Box' step I get the following error when I try to 'vagrant up' from cmd:
D:/Homestead/scripts/homestead.rb:4:in `configure': undefined method `[]' for false:FalseClass (NoMethodError)
from D:/Homestead/Vagrantfile:18:in `block in <top (required)>'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/config/v2/loader.rb:37:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/config/v2/loader.rb:37:in `load'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/config/loader.rb:103:in `block (2 levels) in load'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/config/loader.rb:97:in `each'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/config/loader.rb:97:in `block in load'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/config/loader.rb:94:in `each'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/config/loader.rb:94:in `load'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/vagrantfile.rb:28:in `initialize'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:691:in `new'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:691:in `vagrantfile'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:441:in `host'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:207:in `block in action_runner'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/runner.rb:33:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/runner.rb:33:in `run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:428:in `hook'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:673:in `unload'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/bin/vagrant:177:in `ensure in <main>'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/bin/vagrant:177:in `<main>'
If I use Cygwin to 'Vagrant up' instead I get this error:
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'laravel/homestead' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
The box 'laravel/homestead' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:
URL: ["https://atlas.hashicorp.com/laravel/homestead"]
Error: Could not resolve host: (nil); Host not found
Should I be using Cygwin or cmd?
How can I fix these errors? I ran'Vagrant box' successfully in cmd (pointing to a local .box file as I am behind a proxy), should I have run it in Cygwin instead?
Edit:
Okay, so If i replace '~' with 'C:/Users/[username]/' that brings running it in cmd inline with running it in Cygwin, so the now both give the same error.
The issue was I had used
vagrant box add laravel [location]
rather than
vagrant box add laravel/homestead [location]
I used to start my local VM gc-gw0 with vagrant:
vagrant up gc-gw0
but since today I get this error instead:
/usr/lib/ruby/2.1.0/rubygems/version.rb:202:in `initialize':
Malformed version number string .git (ArgumentError)
from /usr/lib/ruby/2.1.0/rubygems/version.rb:192:in `new'
from /usr/lib/ruby/2.1.0/rubygems/version.rb:192:in `new'
from /usr/lib/ruby/vendor_ruby/vagrant/box_collection.rb:274:in `block (2 levels) in find'
from /usr/lib/ruby/vendor_ruby/vagrant/box_collection.rb:271:in `map'
from /usr/lib/ruby/vendor_ruby/vagrant/box_collection.rb:271:in `block in find'
from /usr/lib/ruby/vendor_ruby/vagrant/box_collection.rb:423:in `block in with_collection_lock'
from /usr/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize'
from /usr/lib/ruby/vendor_ruby/vagrant/box_collection.rb:422:in `with_collection_lock'
from /usr/lib/ruby/vendor_ruby/vagrant/box_collection.rb:264:in `find'
from /usr/lib/ruby/vendor_ruby/vagrant/vagrantfile.rb:157:in `block in machine_config'
from /usr/lib/ruby/vendor_ruby/vagrant/vagrantfile.rb:190:in `call'
from /usr/lib/ruby/vendor_ruby/vagrant/vagrantfile.rb:190:in `machine_config'
from /usr/lib/ruby/vendor_ruby/vagrant/vagrantfile.rb:45:in `machine'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:503:in `machine'
from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:168:in `block in with_target_vms'
from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:192:in `call'
from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:192:in `block in with_target_vms'
from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:174:in `each'
from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:174:in `with_target_vms'
from /usr/share/vagrant/plugins/commands/up/command.rb:67:in `block in execute'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:239:in `block (2 levels) in batch'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:237:in `tap'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:237:in `block in batch'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:236:in `synchronize'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:236:in `batch'
from /usr/share/vagrant/plugins/commands/up/command.rb:58:in `execute'
from /usr/lib/ruby/vendor_ruby/vagrant/cli.rb:42:in `execute'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:258:in `cli'
from /usr/bin/vagrant:173:in `<main>'
The strange thing is, I still started it like this yesterday without problem.
I searched a lot for this error but no hints yet. What does this error message mean? Which is the main error in the whole message?
I use
$ vagrant -v
Vagrant 1.6.5
$ ruby -v
ruby 2.1.2p95 (2014-05-08) [i386-linux-gnu]
Vagrantfile and bootstrap-testnode.sh files are here: rubo77/freifunk-gluon-example-node
But I deleted all my vms in virtualbox but still I get this error anytime I want to do anything with vagrant. seems vagrant has some problem itself. So I guess the scripts I tried have nothing to do with this error.
line 202 in /usr/lib/ruby/2.1.0/rubygems/version.rb is this:
def initialize version
raise ArgumentError, "Malformed version number string #{version}" unless
self.class.correct?(version)
#version = version.to_s.strip.gsub("-",".pre.")
#segments = nil
end
So it seems like ruby is checking a .git folder instead of a version number folder
I found out:
I had created a .git repository inside
~/.vagrant.d/boxes/box-cutter-VAGRANTSLASH-debian77-i386
So vagrant tried to read that folder where there should be only folders named by numbers.
I removed that .git folder and it worked
I got an similar vagrant misconfiguration.
For some reason when updating repos on specific configurations of the vagrant files, this can mess up the vagrant boxes. In my case I was upgrading vagrant and virtualbox with some other changes to the vagrantfile.
I had to go to
~/.vagrant.d/boxes/
and erase the old boxes that I had.
im trying to install cocoapods in a project oy mine, but i get always an error
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.35.0/lib/cocoapods/user_interface/error_report.rb:103: warning: Insecure world writable dir /usr/local in PATH, mode 040777
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/pathname.rb:422:in `open': No such file or directory - /Users/CravenJM/.cocoapods/repos (Errno::ENOENT)
from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/pathname.rb:422:in `foreach'
from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/pathname.rb:422:in `children'
from /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.35.0/lib/cocoapods/sources_manager.rb:63:in `all'
from /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.35.0/lib/cocoapods/user_interface/error_report.rb:130:in `repo_information'
from /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.35.0/lib/cocoapods/user_interface/error_report.rb:34:in `report'
from /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.35.0/lib/cocoapods/command.rb:58:in `report_error'
from /Library/Ruby/Gems/2.0.0/gems/claide-0.7.0/lib/claide/command.rb:300:in `handle_exception'
from /Library/Ruby/Gems/2.0.0/gems/claide-0.7.0/lib/claide/command.rb:274:in `rescue in run'
from /Library/Ruby/Gems/2.0.0/gems/claide-0.7.0/lib/claide/command.rb:264:in `run'
from /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.35.0/lib/cocoapods/command.rb:45:in `run'
from /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.35.0/bin/pod:43:in `<top (required)>'
from /usr/bin/pod:23:in `load'
from /usr/bin/pod:23:in `<main>'
any idea what it could be or how i could fix that? i need cocoapods for an app, but its a nightmare :-)
I had the same error on a new Mac because I forgot to run "pod setup" after installing cocoapods. Because of that the specs repo was missing and the "pod install" command failed.