Question: Is it possible to run the gateway on a container by itself? Running into Socat port 4004 issues

[secbitchris]

Does my trading code have to exist on the same container as the gateway? It seems like localhost is the only recommended way of doing this? Otherwise it's plaintext to the world?

My docker image will not start if I have port 4004 configured.

ports:
  - "${IB_LIVE_PORT:-4001}:4001"      # Live trading API port
  - "${IB_PAPER_PORT:-4002}:4002"     # Paper trading API port
  - "4004:4004"                        # Socat forwarded port
  - "${VNC_PORT:-5901}:5900"          # VNC port mapping

[gnzsnz]

Does my trading code have to exist on the same container as the gateway?

no, it does not have to reside on the same container. having it on the same container is an anti-pattern. here you have some examples #146 (comment)

It seems like localhost is the only recommended way of doing this?

not sure what you mean, in the README.md it's setup in localhost basically because there are too many possible combinations.

check docker networking

Otherwise it's plaintext to the world?

again, it depends on how you set it up. check leaving localhost

[secbitchris]

I think I got it working somewhat. If I run the docker container on my local mac I am able to have my script running on a pve host on the same network talk through it.

So far the socat translation seems to ONLY work when deployed on a mac running docker. It does not appear to work on an ubuntu host. The ports never seem to get advertised.

I'll try some of those examples.

[secbitchris]

Update, managed to figure this out. Thanks for the patience.