<issue_start><issue_comment>Title: vSphere Self Hosted Runner connectivity issue
username_0: Recently I noticed two pipeline failures for vSphere E2E test -

https://github.com/vmware-tanzu/community-edition/actions/runs/1561258503/attempts/1

https://github.com/vmware-tanzu/community-edition/actions/runs/1561244529/attempts/1

Both with the same error

```
The self-hosted runner: vsphere-github-actions-runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
```

Not sure what went wrong in the self hosted runner machine. I checked it just now and noticed this -

```bash
Dec 10 00:34:53 github-actions-runner runsvc.sh[817843]: 2021-12-10 00:34:53Z: Job E2E vSphere Standalone Cluster Test completed with result: Abandoned
```

I haven't found more information as of now but I'll keep this issue updated with latest details and I have rerun the jobs to check if they work now and if everything is good without communication issues with self hosted runner
<issue_comment>username_0: The self hosted runner had some docker containers that were not cleaned up (deleted)

```bash
ubuntu@github-actions-runner:~/actions-runner$ docker ps
CONTAINER ID   IMAGE                                                         COMMAND                  CREATED       STATUS       PORTS                       NAMES
6bcb633c218d   projects.registry.vmware.com/tkg/kind/node:v1.21.2_vmware.1   "/usr/local/bin/entr…"   7 hours ago   Up 7 hours   127.0.0.1:46547->6443/tcp   tkg-kind-c6p9um3b8uslp9k3a1c0-control-plane
02988167cf00   projects.registry.vmware.com/tkg/kind/node:v1.21.2_vmware.1   "/usr/local/bin/entr…"   7 hours ago   Up 7 hours   127.0.0.1:35845->6443/tcp   tkg-kind-c6p9ngrb8ushhnb3d2o0-control-plane
ubuntu@github-actions-runner:~/actions-runner$ 
```
<issue_comment>username_0: Same error in retry - https://github.com/vmware-tanzu/community-edition/actions/runs/1561258503/attempts/2
<issue_comment>username_0: Same error in another retry - https://github.com/vmware-tanzu/community-edition/actions/runs/1561258503/attempts/3
<issue_comment>username_0: Noticed similar failure here too - https://github.com/vmware-tanzu/community-edition/actions/runs/1562684168/attempts/1 , https://github.com/vmware-tanzu/community-edition/actions/runs/1562684168/attempts/2