You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Jon Boone (JIRA)" <ji...@apache.org> on 2018/10/13 11:56:00 UTC
[jira] [Commented] (HADOOP-15802) start-build-env.sh creates an
invalid /etc/sudoers.d/hadoop-build-${USER_ID} file entry
[ https://issues.apache.org/jira/browse/HADOOP-15802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648900#comment-16648900 ]
Jon Boone commented on HADOOP-15802:
------------------------------------
My first thought was to add the '-e' option to the echo command being called in line 64:
??RUN echo "${USER_NAME}\tALL=NOPASSWD: ALL" > "/etc/sudoers.d/hadoop-build-${USER_ID}"??
as this command is running inside a docker container which is running Linux.
> start-build-env.sh creates an invalid /etc/sudoers.d/hadoop-build-${USER_ID} file entry
> ---------------------------------------------------------------------------------------
>
> Key: HADOOP-15802
> URL: https://issues.apache.org/jira/browse/HADOOP-15802
> Project: Hadoop Common
> Issue Type: Bug
> Components: common
> Environment: Ubuntu 18.04 x86_64 running in a VM with 4 CPUs / 8 GBs RAM / 128 GB disk.
> Reporter: Jon Boone
> Priority: Minor
>
> In my Ubuntu 18.04 dev VM, I cloned the hadoop repo and ran the start-build-env.sh script. Once the docker build was completed and the container running, I tried to sudo and it failed. Upon investigation, I discovered that it was creating an entry in /etc/sudoers.d/hadoop-build-${USER_ID} that contained the characters '\t' rather than a tab.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org