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
Chef solo with --user drops permissions after it has created artifacts #8360
Labels
Type: Bug
Does not work as expected.
Comments
btm
added a commit
that referenced
this issue
Apr 11, 2019
Fixes #8360 Signed-off-by: Bryan McLellan <btm@loftninjas.org>
tas50
added
Type: Bug
Does not work as expected.
and removed
Status: Untriaged
An issue that has yet to be triaged.
labels
Apr 11, 2019
btm
added a commit
that referenced
this issue
Apr 15, 2019
Fixes #8360 Signed-off-by: Bryan McLellan <btm@loftninjas.org>
bobchaos
pushed a commit
to cinc-project/chef
that referenced
this issue
Apr 19, 2019
Fixes chef#8360 Signed-off-by: Bryan McLellan <btm@loftninjas.org>
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This fairly bad broke chef-solo by implicitly moving the Dir.chdir("/") early:
Correct behavior:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
When using
chef-solo --user foo --recipe-url
the cache directory (and others) has to be preconfigured to be owned by 'foo'.Chef Version
14.11.21
Platform Version
Ubuntu Linux 18.04.2
Replication Case
from @teknofire:
create /tmp/solo.rb:
then run:
Client Output
The text was updated successfully, but these errors were encountered: