diff --git a/versioned_docs/version-3.8.1/Serving_the_Internet/Install-JATOS-via-Docker.md b/versioned_docs/version-3.8.1/Serving_the_Internet/Install-JATOS-via-Docker.md
index 832a59b61f..c8d41d11d3 100644
--- a/versioned_docs/version-3.8.1/Serving_the_Internet/Install-JATOS-via-Docker.md
+++ b/versioned_docs/version-3.8.1/Serving_the_Internet/Install-JATOS-via-Docker.md
@@ -36,6 +36,8 @@ Also have a look at [JATOS with Docker Compose](/JATOS-with-Docker-Compose.html)
    The `-d` argument specifies to run this container in detached mode (in the background) and the `-p` is responsible for the port mapping.
 
 1. You can check that the new container is running correctly:
+
+   In the following instructions, if you are on a remote host, change `localhost` to your IP/domain.
    
    * Use `docker ps` in the terminal: in the line with `jatos/jatos` the status should say `up`
    * Use curl: `curl http://localhost:9000/ping` should give you `pong` back
@@ -138,4 +140,4 @@ There are two possibilities to update JATOS running in a Docker container:
 
 1. Unless you run [JATOS on multiple nodes](/JATOS-in-a-cluster.html), you can simply use the [auto-update feature](/Update-JATOS.html#automatic-update) to update JATOS to newer versions.
 
-1. Another way, arguably even simpler, is to just change the Docker image tag of JATOS to a newer version. Stop the current running JATOS container and run a new one with the new version tag. **But this only works if you [persist your data with volumes](/Install-JATOS-via-Docker.html#persist-data-with-volumes) - If you don't use volumes your data stored in JATOS will be lost**.
\ No newline at end of file
+1. Another way, arguably even simpler, is to just change the Docker image tag of JATOS to a newer version. Stop the current running JATOS container and run a new one with the new version tag. **But this only works if you [persist your data with volumes](/Install-JATOS-via-Docker.html#persist-data-with-volumes) - If you don't use volumes your data stored in JATOS will be lost**.