Workaround for Chefdk with rbenv

Or just how to fix /opt/chefdk/embedded/bin/ruby: No such file or directory when rehashing on macOS.

A simple error caused by a misunderstood of the functionalities of the rbenv-chefdk plugin.

Treats the embedded Ruby of the ChefDK as another Ruby version so you can manage it with rbenv. But it doesn’t install the ChefDK.

I uninstall the ChefDK because I thought that the plugin provide it. After trying some possible solutions for that “error” I broke everything.

And that’s the reason for the existence of this post and how to recreate it in case you want to distinguish between this error and a real one.

As a friendly reminder, before do anything you should have at least installed:

and avoid having installed the ChefDK.

With the rbenv rehash the error happen at this point:

In the last command execution regardless the current global version that you are using it, you will be using the ChefDK version. But that is just setted superficially after the rehash.

The ChefDK should appear when you list your versions with rbenv versions. Now you can use it whenever you want.

Don’t go and make changes on your environment at 3 AM just because it might look like a good idea.

Related posts:

Life is a continuous name of growth and growth is basically defined as the thing or art from which you are not aware before and after the activity you are well familiar with it. For instance, there…

Before you execute on something, it’s crucial to stipulate all supposed expenses and analysis the common prices associated. Have enough money reserved for the primary 12–16 months for necessities…

Python is one of the most popular and versatile programming languages in the world. It is widely used for web development, data analysis, artificial intelligence, machine learning, automation, and…