[ https://issues.apache.org/jira/browse/YARN-8384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16497051#comment-16497051 ]
Sunil Govindan commented on YARN-8384: -------------------------------------- After YARN-7684, I can see below code snippet in container-executor.c {code:java} char *init_log_path(const char *container_log_dir, const char *logfile) { .. .. if (change_owner(tmp_buffer, user_detail->pw_uid, user_detail->pw_gid) != 0) { .... } .. .. } {code} So ideally here the log file owner is change to the incoming user and group is also take from same. I am not very sure, but this seems like the pblm. cc [~leftnoteasy] [~eyang] > stdout, stderr logs of a Native Service container is coming with group as > nobody > -------------------------------------------------------------------------------- > > Key: YARN-8384 > URL: https://issues.apache.org/jira/browse/YARN-8384 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn-native-services > Reporter: Sunil Govindan > Priority: Major > Labels: docker > > When {{yarn.nodemanager.linux-container-executor.nonsecure-mode.limit-users}} > is set to true, and > {{yarn.nodemanager.linux-container-executor.nonsecure-mode.local-user}} is > set to nobody. > This will cause the docker to run as nobody:nobody in yarn mode. > The log files will be initialized as nobody:nobody: > {noformat} > rw-rr- 1 nobody hadoop 354 May 31 17:33 container-localizer-syslog > rw-rr- 1 nobody hadoop 1042 May 31 17:35 directory.info > rw-r---- 1 nobody hadoop 4944 May 31 17:35 launch_container.sh > rw-rr- 1 nobody hadoop 440 May 31 17:35 prelaunch.err > rw-rr- 1 nobody hadoop 100 May 31 17:35 prelaunch.out > rw-r---- 1 nobody nobody 18733 May 31 17:37 stderr.txt > rw-r---- 1 nobody nobody 400 May 31 17:35 stdout.txt > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org