Repository navigation
running container as user having permission errors #37181
Unanswered
f1-outsourcing
asked this question in
Q&A
Replies: 2 comments
|
I think more information is required to help you. For example, are you using any volumes for the containers, are the containers running in a more restrictive (e.g., SELinux) environment, how did you build the containers. The error appears to be inside the Keycloak container, but without knowing how it is configured, it's hard to tell. |
0 replies
See also the comments on #11286 If you are dealing with an optimized image then primarily it's the data directory that needs to writable. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
When I run the container image (that I created) as docker run -u nobody the application seems to run fine. When I run the same image in a staging environment (with better isolation?) I am getting this error.
I already chown -R nobody /usr/local/keycloak, removed symlinks, don't really know what this is.
What directories in keycloak need to be writable?
still after changing path
com.arjuna.ats.arjuna.exceptions.ObjectStoreException: ARJUNA012225: FileSystemStore::setupStore - cannot access root of object store: /usr/local/keycloak/bin/../data/transaction-logs/ShadowNoFileLockStore/defaultStore/All reactions