Skip to content
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

Using kitchen-nodes with dokken #30

Open
toddmichael opened this issue Nov 30, 2016 · 4 comments
Open

Using kitchen-nodes with dokken #30

toddmichael opened this issue Nov 30, 2016 · 4 comments

Comments

@toddmichael
Copy link

Have had wild success with kitchen-nodes and was happy to get the opportunity to personally thank you, @mwrock, before your HashiConf presentation this year. I just recently started moving all my kitchen-vagrant and kitchen-docker stuff over to kitchen-dokken and have also had great success with it. Today I got to a cookbook that requires kitchen-nodes so I tried converting it from kitchen-docker to kitchen-dokken, but it failed. Is this even possible? If not, no worries. Just always look to implement some consistency in my process is all. Cheers.

Todd Michael

@mwrock
Copy link
Owner

mwrock commented Nov 30, 2016

So glad it has worked for you! To be honest I have never tried with kitchen-dokken. What's the error you get?

@toddmichael
Copy link
Author

Wow man, you are on top of this project! 👍 Here's what I get:

-----> Creating <server-ubuntu-1604>...
       Finished creating <server-ubuntu-1604> (0m4.62s).
-----> Converging <server-ubuntu-1604>...
       Preparing files for transfer
       Preparing dna.json
       Resolving cookbook dependencies with Berkshelf 5.2.0...
       Removing non-cookbook files before transfer
       Preparing nodes
       Preparing validation.pem
       Preparing client.rb
rpc error: code = 13 desc = invalid header field value "oci runtime error: exec failed: container_linux.go:247: starting container process caused \"exec: \\\"sudo\\\": executable file not found in $PATH\"\n"
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>>     Converge failed on instance <server-ubuntu-1604>.  Please see .kitchen/logs/server-ubuntu-1604.log for more details

I'm pretty new to kitchen-dokken, but the fact that I usually configure it as the driver, transport and provisioner coupled with the fact that your project is billed as an extension to the chef-zero provisioner leads me to believe that this is a futile exercise. Would love to be proven wrong though. Let me know if you need more info. Be well.

@ghost
Copy link

ghost commented Oct 24, 2017

@toddmichael hey I am having the same issue as you. Were you ever able to find a solution?

@askz
Copy link

askz commented Jan 7, 2019

Same here, cant find a way to search dokken nodes...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants