06832b94d4
Now that we have working client auth thanks to: https://github.com/barneygale/asyncvnc/pull/4 and related issue, we can use a pw for the vnc server, though we should eventually auto-generate a random one from a docker super obviously. Add logic to the data reset hack loop to do a connection reset after 2 failed/timeout attempts at the regular data reset. We need to also add this logic around reconnectionn events that are due to the host network connection: aka roaming that's faster then timing logic builtin to the gateway. |
||
|---|---|---|
| .. | ||
| README.rst | ||
| docker-compose.yml | ||
| fork_ports_delayed.sh | ||
| ibc.ini | ||
| jts.ini | ||
| run_x11_vnc.sh | ||
README.rst
running ib gateway in docker
We have a config based on the (now defunct) image from "waytrade":
https://github.com/waytrade/ib-gateway-docker
To startup this image with our custom settings simply run the command:
docker compose upAnd you should have the following socket-available services:
x11vnc1@127.0.0.1:3003ib-gw@127.0.0.1:4002
You can attach to the container via a VNC client without password auth.
SECURITY STUFF!?!?!
Though "ib" claims they host filter connections outside localhost (aka 127.0.0.1) it's probably better if you filter the socket at the OS level using a stateless firewall rule:
ip rule add not unicast iif lo to 0.0.0.0/0 dport 4002We will soon have this baked into our own custom image but for now you'll have to do it urself dawgy.