-
Notifications
You must be signed in to change notification settings - Fork 168
knife and berks create many temp directories #133
Comments
The root cause seems to be with Ridley configuration berkshelf/ridley#262 but this bug has been open for some time. The code in question was introduced all the way back in version 1.0.3 of Ridley so this might not just be affecting chefdk but any workstation with berks/knife installed. Related Links: |
Since this an issue in Berks and the bug is reported upstream, I'm going to close it here. If you also see this problem with |
I noticed that running both knife and berks with Chef 11.14 has the problem; since its actually a bug in Ridley. In this case, should is actually be closed here? |
To the best of my knowledge, Chef does not use Ridley |
Chef definitely doesn't use ridley: https://github.com/opscode/chef/blob/281fc5a3a120c2fca42ffe7f8d273debdf530cfe/chef.gemspec#L17-L35 If the issue does exist in Chef then it's probable both codebases have implemented the same bug. We'd need an |
Thanks for the tip, Dan. Using '-rtracer', I've think I have narrowed it down to the knife-spork plugin, specifically Spork Omni, that's included with ChefDK. (snipped for brevity)
|
@bb-anbrown out of curiosity - can you please post your |
Actually, nvm. This is a bug in Ridley. We are making a |
@bb-anbrown @danielsdeleo berkshelf/ridley#276 |
…-fix Pick up mac health check fixes.
Issue is related to berkshelf/ridley#262 and affects both ChefDK 0.1.0 and 0.2.0.
knife
andberks
command creates temporary directories in /tmp of the formdYYYYMMDD-$PID-$RANDOM
.Strace confirms that knife.rb or config.json is not being read prior to temporary directories being created.
The text was updated successfully, but these errors were encountered: