From 4a4d529b33c85682561f1688e216c7aaed844ad4 Mon Sep 17 00:00:00 2001
From: 7heo <7heo@users.noreply.github.com>
Date: Wed, 19 Oct 2016 16:28:48 +0200
Subject: [PATCH] Get rid of unnecessary `-E` flag for `sudo`

In the "Execute Command Example - Sudo Example", the used command is
defining environment variables prematurely, hence requiring the sudo
invocation to be made with the `-E` flag. However, this is not only
necessary but might have indesirable side effects, as the `-E` flag
forwards the whole environment to the subshell.
---
 website/source/docs/provisioners/shell.html.md | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/website/source/docs/provisioners/shell.html.md b/website/source/docs/provisioners/shell.html.md
index 2cdeaa0b7..f693c6ddb 100644
--- a/website/source/docs/provisioners/shell.html.md
+++ b/website/source/docs/provisioners/shell.html.md
@@ -112,13 +112,11 @@ Some operating systems default to a non-root user. For example if you login as
 `execute_command` to be:
 
 ``` {.text}
-"echo 'packer' | {{ .Vars }} sudo -E -S sh '{{ .Path }}'"
+"echo 'packer' | sudo -S sh -c '{{ .Vars }} {{ .Path }}'"
 ```
 
 The `-S` flag tells `sudo` to read the password from stdin, which in this case
-is being piped in with the value of `packer`. The `-E` flag tells `sudo` to
-preserve the environment, allowing our environmental variables to work within
-the script.
+is being piped in with the value of `packer`.
 
 By setting the `execute_command` to this, your script(s) can run with root
 privileges without worrying about password prompts.