Docs: add infos on connecting to host and non linux/amd64 platforms

Author: Conradowatz

Docs/docs/01-Quick-Start/01-Server-Testing.md

@@ -47,6 +47,12 @@ docker run \
 * Line 6: Specifies the Docker image from the TLS-Docker-Library
 * Lines 7-9: Flags passed to the OpenSSL `s_server` binary
 
+:::note
+
+Note, that if you are using a platform beyond linux/amd64 (e.g., on a **Macbook**), you might need to use the parameter `--platform linux/amd64` to correctly start the image.
+
+:::
+
 ### Starting TLS-Anvil
 
 Next, start TLS-Anvil. The current directory is mounted into the Docker container to store the results. We connect to the server using its Docker hostname `openssl-server`, which works because both containers are on the same Docker network.
@@ -78,6 +84,12 @@ docker run \
 * Line 13: Specifies that we want to test a server
 * Line 14: Details how TLS-Anvil should connect to the server
 
+:::tip
+
+If you want to connect to a server running on your host machine, and not in another container, you can either use the hostname `host.docker.internal` or set the docker network to `--network host` and use `localhost` as hostname.
+
+:::
+
 ### What Now?
 
 After the test suite finishes, you should see a folder named `Results_...` containing all the results.  

Docs/docs/01-Quick-Start/02-Client-Testing.md

@@ -49,6 +49,12 @@ docker run \
 * Line 14: Specifies the port TLS-Anvil listens on for client connections
 * Line 15: Provides a script that is executed before each handshake to trigger a new client connection. See explanation below.
 
+:::tip
+
+If you want the trigger script to execute on your host machine, we recommend to run the `TLS-Anvil.jar` executable directly on your host machine using Java 21 or newer. The jar files can be found under [Releases](https://github.com/tls-attacker/TLS-Anvil/releases).
+
+:::
+
 ### Starting the OpenSSL Client Container
 
 :::info
@@ -79,6 +85,12 @@ docker run \
 * Line 6: Specifies the OpenSSL client image from the TLS-Docker-Library
 * Line 7: This argument is passed to the OpenSSL `s_client` binary, which is executed each time a `GET /trigger` request is sent to port 8090
 
+:::note
+
+Note, that if you are using a platform beyond linux/amd64 (e.g., on a **Macbook**), you might need to use the parameter `--platform linux/amd64` to correctly start the image.
+
+:::
+
 ### What Now?
 
 After the test suite finishes, a folder named `Results_...` will appear in your working directory.