diff --git a/docker/README.md b/docker/README.md
index 1913f13..439122c 100644
--- a/docker/README.md
+++ b/docker/README.md
@@ -50,13 +50,6 @@ There is a current issue with the upstream VISSR VISS Server Dockerfile in which
 
 If your project requires Access Grant support please discuss enabling it with the VISSR community.
 
-### Generate `vss_vissv2.binary`
-The VISSR server component requires a file called `vss_vissv2.binary` to understand the VSS tree it must work with. Unfortunately, VISSR provides no default file and you must therefore generate it yourself.
-
-Instructions for doing that can be found in the VISSR documentation site [here](https://covesa.github.io/vissr/server/#vss-tree-configuration)
-
-Tip: The playground maintainers have found that the method involving running `make binary` in a git clone of the VSS source tree to generate the file is straight forward. Note: check the VSS readme for the python requirements for the tooling.
-
 ### Tip: Corporate CA security (download error "tls: failed to verify certificate:")
 If you are working behind a corporate security system that places a _man-in-the-middle_ between your host and the internet you may see security errors when artifacts are downloaded as part of the build process.
 
@@ -172,5 +165,3 @@ The following example uses the javascript HTML client from `vissr/client/client-
   Server: readyState=3, status=200
   Server: {"data":{"dp":{"ts":"2024-01-10T14:56:48Z","value":"Data-not-found"},"path":"Vehicle.Speed"},"ts":"2024-01-10T14:56:48Z"}
 ```
-
-You can query what VSS nodes the server understands by asking for the VSS path list using the URL `http://localhost:8081/vsspathlist`. Entering that URL in your web browser will typically give you a graphical rendering of the JSON data returned.
\ No newline at end of file