-
Notifications
You must be signed in to change notification settings - Fork 168
chefdk preventing vagrant from working #466
Comments
Hello, Hope this helps anyone with the same problem. You will need to make sure that you have installed ChefDK on your machine and that chefdk appears at the beginning of your PATH %HOME%.chefdk\gem\ruby\2.0.0\bin:\opt\chefdk\bin Found a fix whereby you'll have to remove the following gems from your computer, ensuring that you are in the cookbook that you are attempting to run on your VM:- gem uninstall chef chef-zero berkshelf knife-solo This makes certain that you are using the components only installed with ChefDK |
@trekr5 your posts are a little confusing since the first post shows Windows style paths and the second shows Unix paths. If the issue really was that your ChefDK workstation had incorrect paths, you can use the command below in your shell before you start using ChefDK / doing anything chef-related:
and execute the resulting script. If you are using ChefDK from a Windows system using PowerShell, you would do the following:
We're working on a change to make this more obvious on Windows by providing a shortcut on the Start Menu. |
Hi, Apologies. What I should have written was %HOME%chefdk\gem\ruby\2.0.0\bin:\opt\chefdk\bin ! Amended it. Thanks for the tip. |
Thanks for clarifying @trekr5 😄. |
ChefDK 0.8 has the shortcut. Unfortunately there isn't much more we can do to enforce working paths. |
ChefDK#456: Fix ChefDK installation on OS X El Capitan
Hi,
Hoping someone can help.
I'm trying to get a vagrant box to run on my windows computer. My environment has the latest version of ChefDK(0.6.2), berkshelf, ruby 1.9.3 and vagrant.
i have reinstalled Chefdk (version 0.6.2) a number of times and ensured that ChefDK (C:\opscode\chefdk\bin) is installed at the front of the PATH.
However each time when I type in vagrant up, I get the following error...
Can you please tell me how to solve this problem?
The text was updated successfully, but these errors were encountered: