Random result of builds at gitlab.com

The result of building the same commit is very random at gitlab.com, sometimes it runs fine another time the job fails. After a successful build I triggered another build that failed. This looks like the docker daemon isn't started, running the build locally always successful.

gitlab-ci-multi-runner 1.1.4 (9e2fd1a)
Using Docker executor with image fedora ...
ERROR: Failed to create container volume for /cache Get http://unix.sock/v1.18/version: dial unix /var/run/docker.sock: connect: no such file or directory
ERROR: Failed to create container volume for /builds/xxxx Get http://unix.sock/v1.18/version: dial unix /var/run/docker.sock: connect: no such file or directory

ERROR: Build failed: Get http://unix.sock/v1.18/version: dial unix /var/run/docker.sock: connect: no such file or directory

Is there any way of checking the status of the gitlab.com environment.

The same job is successful, fails or even hangs in the middle in the middle of the job when rerun. The build normally takes around 3 minutes to run, yesterday I canceled the job after two hours when the job was hanging at this point of the upgrade.

  Installing  : rsync-3.1.1-8.fc23.x86_64                                 27/85 
  Installing  : less-481-5.fc23.x86_64                                    28/85 
  Installing  : groff-base-1.22.3-6.fc23.x86_64                           29/85

Does anyone else experience the same problem ?

@lbexresearch Looks like the known problem: #1228. We are planning to add some automatic retries in case of docker-engine errors.

Status changed to closed