Closed qiujunda92 closed 5 months ago
secrets will NOT work.
regarding networking, you are publishing your ports on 127.0.0.1, thus you can NOT connect from the outside. This is "very secure".
Try something like
ports:
- "4002:4002" # paper
- "4001:4001" # live
- "5900:5900" # vnc
this is "VERY insecure" but you will be able to connect, if you have your firewall setup correctly. I explain the different options on the README.md
this IS NOT a BUG.
Networking is not my strong point, so I do apologise upfront if this issue sounds trivial/I'm doing anything wrong. It appears that the ports were not open. While
docker-compose up
succeeded, I was unable to connect to IB gateway's API (via ib_async) for further downstream usage. It appears that others had similar issues in the past, and the problem was not solved.To replicate the issue, I used the default ib gateway compose file but edited a few things. Below is my
docker-compose.yml
:I then ran
docker-compose up
in a EC2 instance (Ubuntu 22.04 LTS AMI, r6a.xlarge), where the container spun up successfully. Finally, I attemptedtelnet localhost 4002
andtelnet localhost 5900
, but I got a "Connection refused" error on the former. Only the latter responded correctly. (Interestingly, TightVNC couldn't find the 5900 port on the EC2 instance, so I suspect something is off there too).I also tried this with the
tws-docker-compose.yml
version, but the same issue persists.