Did not find config file: /opt/kitchen/client.rb #105
Comments
|
Is this still an issue for you with 2.4.1? |
|
Getting the same issue with the latest version as well. |
|
Ditto here - basically anytime I try to do a Tried upgrading to |
|
hitting this myself... investigating |
|
Confirmed that downgrading to the ChefDK 2.0.28 serves as a workaround for the time-being. |
|
Found it! 2d01b66 |
|
Newbie in |
|
I upgraded to latest ChefDK (current) with kitchen-dokken 2.6.5 and could still reproduce it at times... I also downgraded to 2.0.28 - and this happens still at times - but not every time (not that repeatable)... |
|
Confirming that this has been an intermittent issue for quite some time before this major blocker popped up. I even have video proof of this in my `Learning Chef for macOS and Linux video' ;-) https://www.safaribooksonline.com/library/view/learning-chef-for/9781491959442/video303777.html I left a take in where I hit this problem so at least people would know how to work around the issue. |
|
Does this go away with ChefDK 2.2.2?
…On Tue, Sep 5, 2017 at 8:44 AM, Mischa Taylor ***@***.***> wrote:
Confirming that this has been an intermittent issue for quite some time
before this major blocker popped up. I even have video proof of this in my
`Learning Chef for macOS and Linux video' ;-)
https://www.safaribooksonline.com/library/view/learning-
chef-for/9781491959442/video303777.html
I left a take in where I hit this problem so at least people would know
how to work around the issue.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#105 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAENzPWKF0Y4FQdlsjvfUTzfFVZt5Rs_ks5sfUIogaJpZM4NWEiu>
.
|
|
I think you meant to say ChefDK 2.2.1. Yes, with the ChefDK 2.2.1 I can converge more than once, so that issue seems to be fixed.
I just installed the new one after the announcement today, so I’ll know more about the intermittent error that happens after `client.rb` once I spend more time using Test Kitchen w/dokken today.
Thanks, looks like your fix addresses the main issue that was preventing us from upgrading to the ChefDK 2.1.11, as not being able to use dokken with Test Kitchen is a deal breaker for us.
… On Sep 7, 2017, at 12:57 PM, Sean OMeara ***@***.***> wrote:
Does this go away with ChefDK 2.2.2?
On Tue, Sep 5, 2017 at 8:44 AM, Mischa Taylor ***@***.***>
wrote:
> Confirming that this has been an intermittent issue for quite some time
> before this major blocker popped up. I even have video proof of this in my
> `Learning Chef for macOS and Linux video' ;-)
> https://www.safaribooksonline.com/library/view/learning-
> chef-for/9781491959442/video303777.html
>
> I left a take in where I hit this problem so at least people would know
> how to work around the issue.
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <#105 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAENzPWKF0Y4FQdlsjvfUTzfFVZt5Rs_ks5sfUIogaJpZM4NWEiu>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#105 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAsfrtjG04xQpiJqG4jFu_CqTfHlOOwtks5sgEqkgaJpZM4NWEiu>.
|
|
So I think newer ChefDK breaks the "chef gem install" to get the latest version of a gem |
|
Look at your /opt/chefdk/bin/kitchen file... it's using exact pins |
|
The main issue is resolved, but the sporadic issue remains. I just saw it today when I ran |
|
This is still a problem in my testing. I'm running ChefDK 2.2.1 on a Mac (newest version for MacOS). One thing to note is that /opt/kitchen is not a valid directory: |
|
I've been trying to do some digging into this and haven't been able to determine what's happening. Obviously a race condition of some kind is the most likely suspect but the code to setup the sandbox seems straightforward and unlikely to result in a race (mkdir+chmod, then simply reference the path in the docker config). I suspect a bug in the overlayfs2 implementation (as in a docker bug) but that's pretty hand-wavey. |
|
kitchen-dokken (2.6.5), same issue when you run |
|
Same issue, running 2.6.5. A simple way of reproducing it is to run in parallel with |
|
So interestingly enough, I ran I have no idea why, but before that, I was having the same issue as everyone else. |
|
This is still an intermittent issue: Doing a kitchen destroy and kitchen test -p seems to consistently work. |
|
@someara I get this error every time with the latest dokken in the latest ChefDK so new everything. It happens every time I try to test a box that already has a running container. |
|
Same problem here with:
|
This will generate the error 90% of the time: Equally, I can avoid the problem 99% of the time by adding So it seems to be a timing issue of some kind. Perhaps between the Linux VM running docker and the macOS host? If so, maybe some |
|
@someara Does the above help? If not, I can do a screen sharing session with you where you can try it out on my system where it is easy to break. |
|
Testing #144 in my own environment and it seems to have fixed the issue. I needed to reset my Docker environment for Dokken though. |
|
This should be fixed by the fix above. I'll get a release out today for this and we'll ship it in the next DK |
|
Hmm, it's still happening for me intermittently. Really not sure the cause. |
|
@tas50 in the meantime, could you recommend a version of |
|
I git cloned commit bbc5ba6 (it says it is release 2.6.7) and did a # Starting from a clean state: nothing in docker and kitchen list is empty.
kitchen destroy && kitchen converge && kitchen destroy && kitchen convergeThe first However, the second So I wouldn't call this closed (yet). |
|
PS: You're missing tags for all the versions after July 2nd, 2017 ( |
|
@docwhat You're right. We didn't have a Rakefile for running rake release and I ran it and didn't notice the whole thing blew up. Too much multitasking for me right now. I pushed the release with the tag and added a Rakefile so we make sure the tags are there in the future. |
|
I still have the issue coming up. I am trying to execute this from jenkins which is running in a container. JenkinsFile: https://github.com/tonan/opsworks-automate-demo/blob/dokken/Jenkinsfile Error |
|
I am working with @tonan on this issue and here are some more details - We are trying to making this work on a Jenkins installation which is running on a docker container. The pipeline script being used is - ..and we end up with the same error. Where are we going wrong? |
|
@mmukherjee I've had similar issues to you. This patch has worked around the issue for me. kitchen-dokken-issue-105.patch.txt diff a/lib/kitchen/helpers.rb b/lib/kitchen/helpers.rb
--- a/lib/kitchen/helpers.rb
+++ b/lib/kitchen/helpers.rb
@@ -248,9 +248,20 @@ EOF
end
def remote_docker_host?
- return false if config[:docker_info]['OperatingSystem'].include?('Boot2Docker')
- return true if config[:docker_host_url] =~ /^tcp:/
- false
+ # Reverts functionality from commit a82bab50
+ #
+ #
+ # Author: Sean OMeara <sean@sean.io>
+ # Date: Tue Jan 24 13:20:31 2017 -0500
+ # Commit: kitchen-dokken 2.0
+ #
+ # Bind mounts data instead of uploading through kitchen-cache container
+ # when talking to a local Docker host. (most use cases)
+ #
+ #
+ # This fixes issue with sibling containers. Discussion in
+ # https://github.com/someara/kitchen-dokken/issues/105
+ return true
end
def sandbox_path |
|
I'm having the same issue when running on CircleCI with a remote docker host. I've tried several workarounds without success. Is there a preferred/documented way to handle this scenario? |
|
@someara is there a specific combination for the dokken driver and chef to make it work. For now if I am taking everything latest, i am facing the same error pretty much everytime in the scenario where kitchen dokken runs within a container. Scenario However if I am running the same converge on my mac or an EC2(ubuntu/centos) vm, with docker installed, it just works fine. (using the latest 2.6.7 kitchen-dokken gem for both scenarios) Is it a current limitation for the kitchen-dokken driver that it errors out when running inside a container. |
|
Following up, as I've chatted with @SauravDevOps in other channels:
For anyone in the thread trying to do this in CI/dokken-inside-docker, that's a different issue entirely and not a use case that is strictly supported at this time. Over the evolution of the driver this may have worked due to different mechanisms being used internally and if there is a working/supported configuration we will make that clear in the readme at that time. |
|
Thankyou @cheeseplus for taking the time to analyze and confirm on the limitation. This would be very helpful for many others like myself who are trying to put in kitchen tests in their pipeline. As the acceptance grows more towards container based CI solutions, this would be a great feature to have. |
|
@cheeseplus do you know if there’s any particular reason why bind mounts are used over volumes? It seems volumes are a more standard, and the recommended, way of dealing with files between host + container. |
|
I can make this error happen 100% in a normal non-DinD setup. Also: |
|
I honestly don't know why bind mounts were chosen - I've only just started digging into the code @ikari7789. @docwhat to make sure we're capturing this - can you do this 100% of the time with 2.6.7 in new DK or just with parallel? |
|
I am unable to reproduce the problem using my test case from above with:
Yay! |
|
I still get this error when running in a DinD chefdk:2.5.8 container. Should I file a new bug, @cheeseplus, for this? I need it in order to do CI on my cookbooks. |
|
You probably should file a new issue but also that's not really a use case that is inherently supported at this time (based on what I've discovered and the intent I've been able to glean from the code). I think the use case was and could be supported but whether that's something that is a bug or feature is in the eye of the beholder :D |
|
I'm using chefdk-3.7.23 and kitchen-dokken 2.6.7 and I'm getting the same errors. Jenkins is running on a VM and not in a container. Suggestions? |
Periodically I receive the following error:
I do not know exactly what causes this but usually I can remedy the situation by doing a
kitchen destroyfollowed by arm -rf ~/.dokkenThe text was updated successfully, but these errors were encountered: