Update README to handle Docker host connection for different setups

- Added instructions for setting DOCKER_HOST variable to host.docker.internal when using Docker Desktop.
- Removed unnecessary defining

Signed-off-by: sinadarbouy <sinadarbouy@gmail.com>

Author: sinadarbouy

getting-started/running-gatewayd.md

@@ -29,10 +29,20 @@ Use the following command to start a PostgreSQL database server inside a contain
 docker run --rm --name postgres-test -p 5432:5432 -e POSTGRES_PASSWORD=postgres -d postgres
 ```
 
-Test your database by running the following command:
+**If `docker0` bridge exists**
 
 ```bash
 DOCKER_HOST=$(ip addr show docker0 | grep inet | grep -v inet6 | awk -F' ' '{ print $2 }' | sed 's/\/16//g')
+```
+
+**if there is no `docker0` bridge (using Docker Desktop)**
+Use the DNS name `host.docker.internal`, which resolves to the internal IP address used by the host.
+```bash
+DOCKER_HOST="host.docker.internal"
+```
+
+Run the following command to test your database:
+```bash
 docker exec -it postgres-test psql postgresql://postgres:postgres@${DOCKER_HOST}:5432/postgres -c "\d"
 ```
 
@@ -120,7 +130,6 @@ Running GatewayD will produce the following log output, which means that Gateway
 GatewayD is running on the host, while PostgreSQL is running inside a container. You can run the following command to test it. Notice that `${DOCKER_HOST}` holds the IP address of the host machine, that is accessible from inside the container.
 
 ```bash
-DOCKER_HOST=$(ip addr show docker0 | grep inet | grep -v inet6 | awk -F' ' '{ print $2 }' | sed 's/\/16//g')
 docker exec -it postgres-test psql postgresql://postgres:postgres@${DOCKER_HOST}:15432/postgres
 ```