Gitlab runner system failure

Summary

CI jobs fail on the start due to "runner system failure". It happens quite often for the last day.

Steps to reproduce

Trigger any pipeline run (this happens randomly).

Actual behavior

The job is failed. The warning banner is showed: There has been a runner system failure, please try again

Expected behavior

The job is started successfully.

Relevant logs and/or screenshots

job log

Running with gitlab-runner 15.11.0 (436955cb)
  on i-092867ece63dca76c-in-767914017133-at-us-east-1 -xFz-2z-, system ID: s_875ea15a3b64
Resolving secrets
00:00
Preparing the "docker" executor
00:03
Using Docker executor with image registry.gitlab.com/<somePath> ...
Authenticating with credentials from job payload (GitLab Registry)
Pulling docker image registry.gitlab.com/<somePath> ...
Using docker image sha256:<someSHA> for registry.gitlab.com/<somePath> with digest registry.gitlab.com/<somePath>@sha256:<someSHA> ...
Preparing environment
00:01
ERROR: Job failed (system failure): prepare environment: Error response from daemon: error while creating mount source path '/mnt/orchlib': mkdir /mnt/orchlib: file exists (exec.go:78:0s). Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information

Environment description

gitlab SAAS; shared runners.

Runner example:

#22957783 (-xFz-2z-F) i-092867ece63dca76c-in-767914017133-at-us-east-1

labels: amd64, computetype-ondemand, glexecutor-docker, group:shared, linux, po, precision-oncology, test

Used GitLab Runner version

Running with gitlab-runner 15.11.0 (436955cb)
  on i-092867ece63dca76c-in-767914017133-at-us-east-1 -xFz-2z-, system ID: s_875ea15a3b64

-->

Possible fixes

Restart the job.