-
Notifications
You must be signed in to change notification settings - Fork 164
metal binary complains about private key #65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The client doesn't ignore the key if you specify it--do you have a ~/.chef/knife.rb, or a .chef/knife.rb in the repository you are presently working in? |
the key is specified in .chef/knife.rb in my repo. I'd like to keep it there for other purposes. However I routinely use chef-zero via chef-client -z and never have this issue. |
Yeah, it certainly shouldn't be happening--I'm not sure at the moment what could be causing it. I iwould have expected the file to get loaded just like normal in the metal executable. |
(chef-client -z is likely loading the .pem as well.) |
@mwrock Both chef-provisioning and chef-client have come a long way: is this still an issue? |
Wow yeah. It has been a while. Just looked at this again and it looks like |
working off of the beta.5 bits, if I run:
I receive this error:
Note that
is output I hacked in to see the server info.
I'm still figuring my way around chef keys but the above key mwrock.pem is a key that is in my knife.rb and configured for an actual chef server. Should a chef-zero run ignore that key?
Thanks!
The text was updated successfully, but these errors were encountered: