Issue Summary

Currently, Bitbucket Runners do not automatically utilize the proxy settings defined in the host's Docker CLI .docker/config.json file. This requires users to manually set the HTTP_PROXY and HTTPS_PROXY environment variables when using a proxy, even if the Docker configuration file is mounted at startup.

Steps to Reproduce

1. Set up Bitbucket Runners with Docker, mounting the host's .docker/config.json file.

   docker container run -it <other args from runner's start command> -v <path_to_docker_config_directory>/.docker:/root/.docker docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-runner

2. Initiate a build that requires internet access through a proxy.

Expected Results

The runner should automatically detect and use the proxy settings from the .docker/config.json file, without needing to manually specify HTTP_PROXY/HTTPS_PROXY environment variables.

Actual Results

The runner does not consider the .docker/config.json file for proxy settings.

Workaround

Users to manually set the HTTP_PROXY and HTTPS_PROXY environment variables for the proxy to be utilized during the build process.