You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now the log and data folder ownership setup may not allow to run the zeebe container with the unprivileged user zeebe that is already setup in Dockerfile due to these directories being owned by the root user:
root@9f6bb138376a:/usr/local/zeebe# ls -al
...
drwxrwxr-x 3 root root 4096 Feb 23 17:26 data
drwxr-xr-x 2 zeebe root 12288 Feb 23 07:59 lib
drwxr-xr-x 2 root root 4096 Feb 23 17:26 logs
whether the issue occurs depends on whether these directories are mounted to volumes and how the permissions for these volumes are setup. This relates to this docker issue, which indicates that at best volumes folders should be pre-created with the desired ownership.
Depending on the setup the zeebe user may lack permission to e.g. write to the logs directory:
Unable to create file /usr/local/zeebe/logs/zeebe.log java.io.IOException: Could not create directory /usr/local/zeebe/logs
megglos
changed the title
Running the zeebe container with the unprivileged user zeebe may fail due to lack of write permissions
Docker: Running the zeebe container with the unprivileged user zeebe may fail due to lack of write permissions
Mar 1, 2023
Describe the bug
As of now the log and data folder ownership setup may not allow to run the zeebe container with the unprivileged user
zeebe
that is already setup in Dockerfile due to these directories being owned by the root user:whether the issue occurs depends on whether these directories are mounted to volumes and how the permissions for these volumes are setup. This relates to this docker issue, which indicates that at best volumes folders should be pre-created with the desired ownership.
Depending on the setup the zeebe user may lack permission to e.g. write to the logs directory:
Relates to https://jira.camunda.com/browse/SUPPORT-15854
The text was updated successfully, but these errors were encountered: