Skip to content
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

CAP_CHOWN vs CHOWN #106

Closed
stevenbarragan opened this issue Nov 16, 2021 · 2 comments
Closed

CAP_CHOWN vs CHOWN #106

stevenbarragan opened this issue Nov 16, 2021 · 2 comments
Labels
question Further information is requested

Comments

@stevenbarragan
Copy link

stevenbarragan commented Nov 16, 2021

What's the difference between CAP_CHOWN and CHOWN in here?

CAP_CHOWN gave me issues on gcloud. I changed to CHOWN and it worked just fine. I could send a PR to change this but I'm not sure about the effects on other platforms. should it be a configurable Value?

@stevenbarragan stevenbarragan added the question Further information is requested label Nov 16, 2021
@revant
Copy link
Collaborator

revant commented Nov 17, 2021

No idea. It was added by a PR.

I could send a PR to change this but I'm not sure about the effects on other platforms. should it be a configurable Value?

try to make it configurable and backward compatible with existing releases.

revant added a commit to revant/helm-1 that referenced this issue Nov 22, 2021
securityContext is configurable from values

closes frappe#105 and frappe#106
@revant
Copy link
Collaborator

revant commented Nov 22, 2021

securityContext will be configurable

@revant revant closed this as completed Nov 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants