Could not find the "brew" executable in /usr/local/bin or anywhere on the path for arm64(M1) about homebrew HOT 11 CLOSED

this issue is related to chef client 17.9.18

from homebrew.

@chadjiang so how did you resolve the issue? Running into it myself using chef client 17.9.26

from homebrew.

We're experiencing the same issue, using Chef client 17.9.26, though its release notes mention that it fixes exactly this issue (present in 17.9.18).

The release notes thank @jweyer8 for fixing it. What might we be doing wrong, Jared?

from homebrew.

@RockLobster @chadjiang

Running Chef client 17.9.26 seems to have fixed the issue for us.

The homebrew_tap resource was trying to reference the 'full' property which was removed in v17.9.18 #12346. Below is the line that was causing the issue:

shell_out!("#{new_resource.homebrew_path} tap #{new_resource.full ? "--full" : ""} #{new_resource.tap_name} #{new_resource.url || ""}",

The fix was as simple as removing the reference to 'new_resource.full' which was causing the no method error due to the fact that the property was removed (The full property was removed by Chef because the --full option was depreciated by Homebrew).

from homebrew.

@RockLobster @jweyer8 @phirk

Chef client 17.9.26 fixed --full issue. but the issue i got before I cannot do brew installl package for ARM64 (m1) machine, the brew installation path in the node is /opt/homebrew,

in the node , /opt/chef/embedded/lib/ruby/gems/3.0.0/gems/chef-17.9.26/lib/chef:

resource/homebrew_tap.rb
resource/homebrew_cask.rb
mixin/homebrew_user.rb.
provider/package/homebrew.rb

those file use /usr/local/Homebrew for brew. I have to update them in the node to make installation work.

from homebrew.

@chadjiang

Have you tried specifying the install path with the homebrew_path property?

To use your example, would the following fix your issue:

homebrew_cask 'Install Chrome' do
cask_name 'google-chrome'
homebrew_path '/opt/homebrew/bin/brew'
end

from homebrew.

@jweyer8
ha, good to know. I did not realize this :homebrew_path parameter. Thanks a lot!

from homebrew.

@chadjiang
No problem!

from homebrew.

oh, that looks interesting, will try on Monday if that solved our issue!

from homebrew.

I needed to apply two changes:

1. even though homebrew got installed, it didn't get added to the path, leading homebrew_user.rb to fail.
   I fixed it by adding the following lines to my default.rb:

include_recipe 'homebrew'
ENV['PATH']="#{ENV['PATH']}:/opt/homebrew/bin:/opt/homebrew/sbin"

2. Even though it's now part of the path, all homebrew_cask, homebrew_tap require setting homebrew_path.

Note: Just doing 2.) is not enough because homebrew_user.rb will still fail.

from homebrew.

Weirdly enough, homebrew_package / package does not have a homebrew_path and is working just fine

from homebrew.