-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Problems when using container with read-only root FS #69
Comments
Edit 2: I didn't specify the correct bundle destination, my mistake! Ok, so I set the root FS to the default behaviour (read and write). I still am having problems.
The permissions look correct. The file is present. KPM still fails. Edit: I have a security context config in place, so that the container runs as the
Container security context:
|
I am trying to deploy KAUI on kubernetes and also fulfill some security requirements. One common thing is a read-only root filesystem. The app then can write only to mounted volumes under some path (if volume is not set as read-only) - for example: mount an empty dir to
/tmp
for temporary data.Well I tried
kpm pull_defaultbundles
but it failed on a tempdir creation.I am using the image you supply (
docker.io/killbill/kaui:2.0.11
) so it runs under tomcat. I am not sure, how to specify a temp directory (via an env. variable for example). I triedTMPDIR
,TMP
andTEMP
, but it still tries to write at/var/lib/tomcat/...
. I also looked through the source code in ruby, but I think, it should work. On the other hand, I am not sure, how the default behaviour is altered by running the app under jRuby (creating a "sandbox" in the app's folder or something?).Is there a way to specify the path? Am I missing something?
The text was updated successfully, but these errors were encountered: