sc/installation(docker): replace Running the Sauce Connect Docker Container with a CI/CD Pipeline with links to readiness check

Author: mmatczuk

docs/secure-connections/sauce-connect-5/installation/docker.md

@@ -43,58 +43,22 @@ Here are some benefits/use cases for using containerized Sauce Connect Proxy:
        --network="host" \
        -it saucelabs/sauce-connect:5.0
    ```
+   If desired, you can specify any additional [`sc run` options](/dev/cli/sauce-connect-5/run/) as environment variables.
 
-If desired, you can specify any additional ["sc run" CLI arguments](/dev/cli/sauce-connect-5/run/).
+   Alternatively, you can also mount a config file to the container by adding the `-v` option to the `docker run` command.
 
-:::note
-The example above uses `--network="host"` docker option to allow Sauce Connect in the Docker container to access your local services in the host machine. This option does not work on MacOS and Windows. See [Connect from a container to a service on the macOS host](https://docs.docker.com/desktop/networking/#use-cases-and-workarounds) for more details.
-:::
-
-## Running the Sauce Connect Docker Container with a CI/CD Pipeline
-
-If you want to run this Docker image as part of your CI/CD pipeline, you would need a way to determine that Sauce Connect Proxy is ready to proxy the requests. You can achieve that by:
-
-- Using the `/readyz` endpoint, available with the Sauce Connect Proxy [internal API server](/secure-connections/sauce-connect-5/operation/monitoring/#local-api-server).
-
-### Readiness Endpoint
-
-The readiness endpoint allows you to configure liveness and readiness HTTP probes. See the [Kubernetes documentation](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/) for more information.
-
-Docker container exposes Sauce Connect Proxy [API server](/secure-connections/sauce-connect-5/operation/monitoring/#local-api-server) on port 8032. The readiness endpoint `/readyz` returns 200 response code when Sauce Connect Proxy is ready, 503 otherwise.
-
-You can leverage the readiness endpoint in your CI/CD pipeline by running the following:
-
-1. Create a bash script `wait-for-sc.sh` that will ensure the pipeline only continues after Sauce Connect Proxy is fully connected and ready.
-
-   ```bash title="wait-for-sc.sh"
-   timeout=45
-   i=0
-   until [ "$(curl -s -o /dev/null -w ''%{http_code}'' localhost:8032/readyz)" == "200" ]
-   do
-       let "++i"
-       if [ $i -gt $timeout ]; then
-          echo "Timed out after $i seconds waiting for Sauce Connect readiness, exiting..."
-          exit 1
-       fi
-       sleep 1
-   done
-   echo "SC ready"
+   ```bash
+   $ docker run \
+       -v /path/to/config.yaml:/etc/sauce-connect/sauce-connect.yaml \
+       --network="host"\
+       -it saucelabs/sauce-connect:5.0
    ```
 
-1. Run Sauce Connect Docker container using the script below. It is important that you map port 8032 (that is, `-p 8032:8032`) so that the port is available to the host.
+See [Sauce Connect Proxy Readiness Checks](/secure-connections/sauce-connect-5/operation/readiness-checks) for more information on how to check if the tunnel is ready to accept jobs.
 
-```bash
-$ docker run \
-    --detach \
-    -e SAUCE_USERNAME=${SAUCE_USERNAME} \
-    -e SAUCE_ACCESS_KEY=${SAUCE_ACCESS_KEY} \
-    -e SAUCE_REGION=${SAUCE_REGION} \
-    -e SAUCE_TUNNEL_NAME=${SAUCE_TUNNEL_NAME} \
-    -p 8032:8032 \
-    -t saucelabs/sauce-connect:5.0 \
-    -i your-docker-tunnel
-  $ ./wait-for-sc.sh
-```
+:::note
+The example above uses `--network="host"` docker option to allow Sauce Connect in the Docker container to access your local services in the host machine. This option does not work on MacOS and Windows. See [Connect from a container to a service on the macOS host](https://docs.docker.com/desktop/networking/#use-cases-and-workarounds) for more details.
+:::
 
 ## Additional Resources