Linux CPU Build fails with can't connect to docker daemon

[seemethere]

https://github.com/pytorch/pytorch/actions/runs/8738940413/job/23979092050

Relevant lines:

Cannot connect to the Docker daemon at unix:///run/docker/docker.sock. Is the docker daemon running?
"docker stop" requires at least 1 argument.
See 'docker stop --help'.

Usage:  docker stop [OPTIONS] CONTAINER [CONTAINER...]

Stop one or more running containers
"container prune" requires API version 1.25, but the Docker daemon API version is 1.24

[seemethere]

Have a feeling that this might be related, actions/actions-runner-controller#2999

[zxiiro]

@danibaibak mentioned on Slack that this appears to be intermittent. Retrying the failed jobs could allow them to pass. This is going to be harder to troubleshoot since it doesn't appear to happen on every run.

One theory right now is since dind-rootless mode runs docker daemon in a sidecar container. Perhaps the sidecar is not ready yet when the arc runner starts accepting jobs. I'm not sure how to validate that theory though.

[ZainRizvi]

Another manifestation: https://github.com/pytorch/pytorch/actions/runs/8803473291/job/24161684387

[zxiiro]

I don't know if this is related but sounds similar actions/actions-runner-controller#3257