Rsync Permission Denied - Subsequent Runs

[smdern]

After I run knife solo bootstrap as the root user, I want to switch and use a different user for subsequent runs. I'm running into an issue where rsync can't sync due to permission denied. I've been blowing away the tmp/chef-solo dir and running again, so the new user now owns the tmp/chef-solo dir. I'm pretty sure that any user w/ sudo permission should be allowed to run chef-solo.

Any thoughts?

[smdern]

I was looking @ def rsync_kitchen and I wonder if it would be good to just set permissions of the directory to 666.. I can't see any reasons why you'd want prevent other people from writing in the tmp directory.

[tmatilai]

The problem is that Chef's cache dir is used by knife-solo to sync its own data. This has already quite a few issues, at least #12, #86, #128 and #145. The last has a on-going work to solve the problem. (The others could maybe be closed?)

The /tmp is already a security problem (#1), and making it world writeable doesn't sound good.

So, sorry. No solution yet. :/

[ifeltsweet]

Exact same problem. Really want this to be fixed.

[matschaffer]

If you could try out #145 and report success/failure that would be a big help! Planning to roll that out soon but it may require removing custom solo.rb support.

[tmatilai]

I'll close this as there are already a couple of issues for the same problem.

[benissimo]

Why isn't /tmp/chef-solo deleted at the end of each run?

[matschaffer]

The intent was to avoid extra time spent transferring cookbooks (since we
use rsync).

The latest prerelease uses $HOME by default which should avoid some of
these issues.

On Monday, June 3, 2013, Ben Ellis wrote:

Why isn't /tmp/chef-solo deleted at the end of each run?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/177#issuecomment-18852209
.

-Mat

about.me/matschaffer