Yukihiko SAWANOBORI

[clabot:check]

Sorry it took me so long to answer. In such a case, writing the path of the client in `knife.rb` will work. ``` Chef::Config[:chef_client_path] = "/usr/local/bin/chef-client" ```

What version of Chef are you using on the local workstation and what version are you installing on the remote node? For example, would the same thing happen if both...

Also, some information about the execution environment of the remote node might help. For example, the OS version, whether the platform is a public cloud instance or a Private Cloud...

Once I have detailed usage information, I can figure out what to do. However, if you want to continue to use Chef 16 or lower on your WorkStation, you can...

sorry for delay. If chef-zero completely removes the HTTP interface and there is no option to use it, maintaining knife-zero will be difficult. As of now there are no plans...

However, since the socketless server is also based on Rack interface, it is possible to implement TCP listeners with knife-zero. It depends on the motivation of me or the contributors.

Thanks @limitusus , If tcp socket mode is deleted, this test will fail, so we will consider if we can deal with it later. https://circleci.com/gh/higanworks/knife-zero/tree/integration_testedge

@darkn3rd Thanks, and don't worry about it. knife-zero already turns on `--listen` option by default since `v1.18.1`. https://github.com/higanworks/knife-zero/blob/master/CHANGELOG.md However, Chef's RFC could be interpret the `--listen` option someday to disappear....

@EugenMayer We have not solved the fundamental concern that the core might delete the function, and the WARN message will continue to be displayed. However, it does not need to...