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

Chef binary was not found #116

Open
fletchowns opened this issue Jan 15, 2015 · 0 comments
Open

Chef binary was not found #116

fletchowns opened this issue Jan 15, 2015 · 0 comments

Comments

@fletchowns
Copy link

I had to uninstall Vagrant 1.7.2 and downgrade to 1.6.5 (because of this issue) and now I'm seeing the following error message on initial vagrant up:

==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => C:/Users/fletchowns/git_repos/nexus-cookbook
    default: /tmp/vagrant-chef-3/chef-solo-1/cookbooks => C:/Users/fletchowns/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150114-5456-1jpry17-default
==> default: Running provisioner: chef_solo...
The chef binary (either `chef-solo` or `chef-client`) was not found on
the VM and is required for chef provisioning. Please verify that chef
is installed and that the binary is available on the PATH.

Not sure why I didn't run into this until now, but it looks like it can be fixed by adding:

config.omnibus.chef_version = :latest
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

1 participant