Issue Summary

When Starting a Runner, it's possible to change the working directory internal and external mount paths:
https://support.atlassian.com/bitbucket-cloud/docs/set-up-and-use-runners-for-linux/#Changing-the-working-directory-of-your-runner

For example:

docker run [all existing parameters] -v /mydir:/mydir -e WORKING_DIRECTORY=/mydir

However, if the paths from the command above on -v and -e flags don't match, the Runner will start correctly, but builds with fail with the following error message:

Unable to run script in container <container_UUID> and inspect it's state

Steps to Reproduce

1. Create a new Runner in Bitbucket Cloud
2. Copy the Runner start command, and change the working directory internal and external mount paths to different paths, for example:

   docker run [all existing parameters] -v /mydir1:/mydir2 -e WORKING_DIRECTORY=/mydir2
   

Expected Results

Runners will be able to start properly, even if the internal and external mount paths don't match.

Actual Results

The Runner will fail to start with the error below:

Unable to run script in container <container_UUID> and inspect it's state

Workaround

The internal mount path must match the external mount path for all Runner builds.