Process not started

I don’t often use the word no, but no. The docker container specifically doesn’t run as root, runs as a user. You can tell kubernetes to run it as root (which I won’t help with and strongly discourage), but to add sudo you’d need to be root, and at that point, you don’t need sudo.

The solution is the same as when you asked it in your previous thread.

Extend the container, add what you need, and then use that container in helm.

1 Like