-
Notifications
You must be signed in to change notification settings - Fork 92
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
kitchen create fails when container does not exist #208
Comments
Same thing happens to me on:
|
When using However, when using |
@anapsix only action i'm able to do is |
Unfortunately seeing the same behaviour with 2.10.0. |
can confirm downgrading to the following versions has fixed the issue:
@shoekstra thank you! this unblocks me. |
I suspect this is related to the fact that the docker-api gem has been upgraded to 2.x and the API has likely changed and we need to account for that in this plugin. Anyone have time or willing to looking into this further to see what the fix might be? |
Downgrading to Chef Workstation 20.8.11 worked for me. Then you don't need to mess around with gems. Workstation 20.8.11 bundles:
|
@devopsdina this is indeed a perfect fix for this issue |
ran into the same - Excon::Error::Socket issue while trying to on version "20.12.187" for Mac kitchen verify
|
Description
kitchen converge
causes the following errorVersion
Environment
Scenario
Opinion after some debugging
there is a problem with getting container info, the
conn.get
call fails.Steps to Reproduce
kitchen converge on this kitchen.yml
Expected Result
no error is expected
Actual Result
➕ Additional context
debug log
kitchen diagnose --all
The text was updated successfully, but these errors were encountered: