From 1959ca6f231f9a1fdebba0c70f6e850b0ab4d635 Mon Sep 17 00:00:00 2001
From: Takanobu Asanuma <tasanuma@apache.org>
Date: Tue, 13 Nov 2018 13:57:07 +0900
Subject: [PATCH] HADOOP-15912. start-build-env.sh still creates an invalid
 /etc/sudoers.d/hadoop-build-${USER_ID} file entry after HADOOP-15802.
 Contributed by Akira Ajisaka.

(cherry picked from commit a67642c3776156ee941f12f9481160c729c56027)
---
 start-build-env.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/start-build-env.sh b/start-build-env.sh
index 6c8ddb331b1..284f8892e7d 100755
--- a/start-build-env.sh
+++ b/start-build-env.sh
@@ -61,7 +61,7 @@ docker build -t "hadoop-build-${USER_ID}" - <<UserSpecificDocker
 FROM hadoop-build
 RUN groupadd --non-unique -g ${GROUP_ID} ${USER_NAME}
 RUN useradd -g ${GROUP_ID} -u ${USER_ID} -k /root -m ${USER_NAME}
-RUN echo -e "${USER_NAME}\tALL=NOPASSWD: ALL" > "/etc/sudoers.d/hadoop-build-${USER_ID}"
+RUN echo "${USER_NAME} ALL=NOPASSWD: ALL" > "/etc/sudoers.d/hadoop-build-${USER_ID}"
 ENV HOME /home/${USER_NAME}
 
 UserSpecificDocker