From c75cadf00784e271c5372fabe73dfd9e9a5632cd Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Wed, 23 Mar 2016 13:00:04 +0000 Subject: [PATCH] more correct sudo scoping we want to know whether systemctl can be run when sudoing. This shouldn't fix #2090, only give is a different error. --- test/640_proxy_restart_reattaches_test.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/640_proxy_restart_reattaches_test.sh b/test/640_proxy_restart_reattaches_test.sh index 7407d18d..44442b3d 100755 --- a/test/640_proxy_restart_reattaches_test.sh +++ b/test/640_proxy_restart_reattaches_test.sh @@ -52,7 +52,7 @@ sleep 1 check_attached # Restart docker itself, using different commands for systemd- and upstart-managed. -run_on $HOST1 sh -c "command -v systemctl >/dev/null && sudo systemctl restart docker || sudo service docker restart" +run_on $HOST1 sudo sh -c "command -v systemctl >/dev/null && systemctl restart docker || service docker restart" wait_for_proxy $HOST1 sleep 5 # allow for re-tries of attach # Re-fetch the IP since it is not retained on docker restart