Change SETUP_NODE to True for node e2e docker validation test.

[Random-Liu]

The continuous node e2e docker validation test is failing because:

W0722 00:48:52.163940    1265 image_list.go:85] Could not pre-pull image gcr.io/google_containers/netexec:1.4 exit status 1 output:  Cannot connect to the Docker daemon. Is the docker daemon running on this host?

This is because jenkins is not added to docker user group.
For other images tested in node e2e, jenkins is added to docker user group when the images are initially created https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/environment/setup_host.sh#L102.

However, in node e2e docker validation test, we are using GCI image which doesn't do that.
So we should use the SETUP_NODE option to add user to docker group before test running

kubernetes/test/e2e_node/e2e_remote.go

Lines 150 to 159 in b6c8790

	if setupNode {
	uname, err := user.Current()
	if err != nil {
	return "", false, fmt.Errorf("could not find username: %v", err)
	}
	output, err := RunSshCommand("ssh", GetHostnameOrIp(host), "--", "sudo", "usermod", "-a", "-G", "docker", uname.Username)
	if err != nil {
	return "", false, fmt.Errorf("instance %s not running docker daemon - Command failed: %s", host, output)
	}
	}

.

This is only one line change, could you help me review the PR? @wonderfly
Thanks a lot! :)

[wonderfly]

LGTM

[Random-Liu]

@k8s-bot test this issue #IGNORE.

[Random-Liu]

Apply LGTM based on #29435 (comment).

[Random-Liu]

The test keeps failing, bump up the priority.

[k8s-bot]

GCE e2e build/test passed for commit 7b27358.

• Test Results
• Build Log
• Test Artifacts
• Internal Jenkins Results

[k8s-github-robot]

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

[k8s-bot]

GCE e2e build/test passed for commit 7b27358.

• Test Results
• Build Log
• Test Artifacts
• Internal Jenkins Results

[k8s-github-robot]

Automatic merge from submit-queue