-
Notifications
You must be signed in to change notification settings - Fork 47
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
[Kubernetes] Breaks on Kubernetes ReadOnlyFileSystem #39
Comments
Hi @Moep90 We will have to investigate this, but not quite sure when, since this issue hasn't been bought up by others that use SuperTokens on Kubernetes. Maybe you could fork our repo and make your own docker image? We have instructions on how to do that here: https://github.com/supertokens/supertokens-core/wiki/Building-from-source#creating-a-docker-image |
I assume they either build their container or helm chart 🤷 https://github.com/supertokens/supertokens-docker-postgresql/blob/master/helm-chart/values.yaml#L94 |
Not quite sure. The helm chart is community contributed. |
It is currently impossible to run the docker image in a Kubernetes cluster with specific security requirements, such as a ReadOnlyRootFilesystem and/or another UID. |
Oh yea, I get that. Which is why i suggested to create your own docker image from the link above without the chown command in it. We can further investigate if we can remove that from our repo, but, not quite sure about the timeline for that, unless there is a lot of interest in this issue. |
On a ReadOnlyFileSystem Pod in Kubernetes, you got many Read-only file system errors
There are many chown commands in the entry point; could they be make it optional?
For Instance as an ENV
supertokens-docker-postgresql/docker-entrypoint.sh
Line 39 in e6a6dae
The text was updated successfully, but these errors were encountered: