Installing Chef-DK on OSX to non-system drive results in broken scripts

[bklang]

In the installer you can select the drive onto which you want Chef-DK installed. In my case, I selected my secondary drive and the installer ran successfully. The secondary drive is mounted at /Volumes/Morningside, but the Chef scripts' shell prelines are not updated appropriately:

$ head -n 1 /Volumes/Morningside/opt/chefdk/bin/*
==> /Volumes/Morningside/opt/chefdk/bin/berks <==
#!/opt/chefdk/embedded/bin/ruby

==> /Volumes/Morningside/opt/chefdk/bin/chef <==
#!/opt/chefdk/embedded/bin/ruby

==> /Volumes/Morningside/opt/chefdk/bin/chef-apply <==
#!/opt/chefdk/embedded/bin/ruby

This path should point to /Volumes/Morningside/opt/chefdk/embedded/bin/ruby

[bklang]

Actually, the problem goes deeper. Trying to execute Ruby has problems because of the compile-time linker path:

The following berks command failed to execute:

    /Volumes/Morningside/opt/chefdk/bin/berks --version --format json

The stdout and stderr are shown below:

    stdout:
    stderr: dyld: Library not loaded: /opt/chefdk/embedded/lib/libruby.2.1.0.dylib
  Referenced from: /Volumes/Morningside/opt/chefdk/embedded/bin/ruby
  Reason: image not found

Perhaps the installer should disable non-root disks, since it doesn't appear to be supported?

[danielsdeleo]

This is a bug in the omnibus packaging system, so I filed a bug over there chef/omnibus#397

[danielsdeleo]

The upstream bug has been fixed so this should be resolved in a future release.