meklu opened a new pull request #13708:
URL: https://github.com/apache/pulsar/pull/13708


   If you don't set the SELinux context of volumes in compose files, there
   will be access errors all over the place. This change addresses that
   issue in the kitchen-sink sample compose file.
   
   ### Motivation
   
   On Linux distributions with SELinux enabled, the current 
docker-compose/kitchen-sink example fails to start. This is because SELinux 
denies reading or executing any files from within the container that do not 
have the proper SELinux context specified.
   
   ### Modifications
   
   This pull request adds the `:z` modifier (which "indicates that the bind 
mount content is shared among multiple containers") to the used volumes.
   See https://docs.docker.com/storage/bind-mounts/#configure-the-selinux-label 
for more information.
   
   ### Verifying this change
   
   - [ ] Make sure that the change passes the CI checks.
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   ### Does this pull request potentially affect one of the following parts:
   
   *If `yes` was chosen, please highlight the changes*
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API: (no)
     - The schema: (no)
     - The default values of configurations: (no)
     - The wire protocol: (no)
     - The rest endpoints: (no)
     - The admin cli options: (no)
     - Anything that affects deployment: *(don't know)*
         - the added SELinux labels shouldn't affect non-SELinux systems
   
   ### Documentation
   
   Check the box below or label this PR directly (if you have committer 
privilege).
   
   Need to update docs? 
   
   - [ ] `doc-required`
   - [x] `no-need-doc`
       -  This pull request only changes example docker-compose files.
   - [ ] `doc`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to