a140262 opened a new issue, #323:
URL: https://github.com/apache/incubator-uniffle/issues/323

   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   
   
   ### Search before asking
   
   - [X] I have searched in the 
[issues](https://github.com/apache/incubator-uniffle/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### Describe the bug
   
   My Spark application's UID is different from GroupID, ie. uses 999:1000 to 
access /data/rssadmin. In the [init container 
command](https://github.com/apache/incubator-uniffle/blob/e6b4260aa54a9ffda30ec02fa050be1c108e8a9f/deploy/kubernetes/operator/pkg/controller/util/util.go#L214),
 why do you setup the permission via GID:GID instead of the format of UID:GID 
for the host paths? 
   The pod securityContext I set is:
   ```
       securityContext:
         runAsUser: 999
         fsGroup: 1000
   ```
   
   Both coordinator and server pods threw the permission error:
   ```
   /data/rssadmin/rss/bin/start-coordinator.sh: line 73: 
/data/rssadmin/rss/logs/coordinator.out: Permission denied
   AND
   /data/rssadmin/rss/bin/start-shuffle-server.sh: line 96: 
/data/rssadmin/rss/logs/shuffle_server.out: Permission denied
   ```
   
   
   
   ### Affects Version(s)
   
   0.7.0-snapshot
   
   ### Uniffle Server Log Output
   
   _No response_
   
   ### Uniffle Engine Log Output
   
   _No response_
   
   ### Uniffle Server Configurations
   
   _No response_
   
   ### Uniffle Engine Configurations
   
   _No response_
   
   ### Additional context
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!


-- 
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: dev-unsubscr...@uniffle.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to