Note in README the possibility to use on a separate host (#9)

README.md

@@ -22,9 +22,12 @@ See [Go's Getting Started](https://golang.org/doc/install) if your package manag
 
 `go-mmproxy` has to be ran:
 
-- on the same server as the proxy target, as the communication happens over the loopback interface;
+- on the same server as the proxy target, as the communication happens over the loopback interface<sup>1</sup>;
 - as root or with `CAP_NET_ADMIN` capability to be able to set `IP_TRANSPARENT` socket opt.
 
+<sup>1</sup> This is not a hard requirement, and with routing magic go-mmproxy can be ran on a different host than the target(s).
+See the [docker-example directory](https://github.com/kzemek/go-mmproxy/tree/main/docker-example) for a working example.
+
 ## Running
 
 ### Routing setup