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.

Sign up for GitHub

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

Jump to bottom

Support initContainers #170

Open
eve0415 opened this issue Mar 31, 2024 · 1 comment · May be fixed by #248
Open

Support initContainers #170

eve0415 opened this issue Mar 31, 2024 · 1 comment · May be fixed by #248
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@eve0415
Copy link

eve0415 commented Mar 31, 2024

My instance (volumes) can only be written by UID 0 (root) normally unless i change the ownership of the files/directories that are mounted using initContainers before the main containers start.
Or support changing the UID/GID (runAsUser, runAsGroup) but this is not recommended way.
@Pothulapati Pothulapati added good first issue Good for newcomers help wanted Extra attention is needed labels May 8, 2024
@gdsoumya gdsoumya linked a pull request Oct 11, 2024 that will close this issue
Open
@gdsoumya
Copy link

@eve0415 / @Pothulapati I raised a PR to allow adding custom init containers, let me know if that works like you expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(crd): allow adding custom init containers to dragonfly sts gdsoumya/dragonfly-operator
3 participants
@Pothulapati @eve0415 @gdsoumya