Issue Summary

Steps running on the Linux Docker self hosted runner will occasionally error with the follow message

Status 404: {"message":"No such container: c163754c-b662-526d-a2d8-a33dd58e1577_22e17898-6287-4f39-aa4d-5eb86438112a_system_auth-proxy"} Refer to the Troubleshooting runners document for help resolving the issue. 

Steps to Reproduce

1. Run a step on a self hosted Linux Docker runner.
2. Observe if the step errors.

Expected Results

The step should execute.

Actual Results

1. step errors before the build script is executed.

Workaround

1. Re-run step: The Step can be re-run.
2. Increase the amount of CPU/disk/memory resources allocated to the self hosted runner - the root cause is a delay in Docker creating the container - ensuring Docker has adequate CPU, memory and minimal disk contention may reduce the frequency of this error.