-
Notifications
You must be signed in to change notification settings - Fork 30
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
Bug: Chart has expectations that should be overriden (running as root) #78
Comments
This was something that might have come up from https://github.com/SQLJames/factorio-server-charts/pull/69/files when the nfs permissions were addressed, I dont think you need to run as root but the user is required as it runs as the docker user that was specified. Please see the release notes. If you could test using that user it might resolve this issue. |
Unfortunately seems to make no difference.
|
Had to manually in the already existing pvc to chown them properly, otherwise it wouldn't work. I think there should be a way to disable the chmod part of that. |
i am currently working on mutible charts to seperate sidecars in individual deployments and add "plugins".
all sidecars (config-init, mod-download, save-import, port-fixer) run with these:
but the factorio server itself does not work with read only fs.
i thought i would submit my charts as "new" ones to this repo.
but there is also a catch: i want to open a dedicated discussion about it to better know how and if this would be accepted. still need to cleanup the charts and finalize stuff before going public. but everything is already working (at least on my cluster) and i migrated my factorio deployments to those charts. |
The chart or more exactly volume-permissions init-container has the expectation that it runs as root.
This needs a way to not have such an expectation without the ability to disable it.
Running with the following securityContext:
This results in the init-container exiting with non-successful status and thus the pod will not start.
The text was updated successfully, but these errors were encountered: