Skip to content
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.

Hardcoded "opscode" path #251

Closed
dandv opened this issue Dec 1, 2014 · 1 comment
Closed

Hardcoded "opscode" path #251

dandv opened this issue Dec 1, 2014 · 1 comment

Comments

@dandv
Copy link

dandv commented Dec 1, 2014

I've just installed ChefDK on Windows in a directory I chose, and vagrant up died with :

Bringing machine 'default' up with 'virtualbox' provider...
The following berks command failed to execute:

    C:\utils\chef\chefdk\bin/berks.BAT --version --format json

The stdout and stderr are shown below:

    stdout:
    stderr: C:/Utils/chef/chefdk/bin/berks:38:in `load': cannot load such file -- C:/opscode/chefdk/embedded/apps/berkshelf/bin/berks (LoadError)
        from C:/Utils/chef/chefdk/bin/berks:38:in `<main>'

I replaced opscode with the actual path in all files under bin, but I still get errors:

C:\Vagrant\meteor>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
    default: The Berkshelf shelf is at "C:/Users/A/.berkshelf/vagrant-berkshelf/shelves/berkshelf20141130-6800-1yco55z-default"
==> default: Sharing cookbooks with VM
There are errors in the configuration of this machine. Please fix
the following errors and try again:

Berkshelf:
* berksfile_path must be set

If opscode is the only directory that works, then maybe an option would be to remove the directory choice from the install wizard.

Posted initially at berkshelf/berkshelf#1347 - please close in whichever repo is less appropriate.

@danielsdeleo
Copy link
Contributor

Duplicates #68 -- this is fixed in master.

@chef-boneyard chef-boneyard locked and limited conversation to collaborators Feb 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants