Open buzzcloudau opened 8 years ago
Sorry for the late response.
Can you tell me what did you try exactly? I never tried running VNC in fact. How did you test this and how did you see you could not connect?
I see there's quite a few differences with the link you provided, it exposes the 5900 port for example. Can you try adding that to the Dockerfile and see if it works?
I do have this working locally, but my script needs a lot of cleaning up before I can publish it.
Although I have modified it pretty heavily, it is still using parts of your script so I will publish it as a fork of this project soon.
Thanks.
Awesome, although if you want you can just put it in a gist, or just copy paste it here. That's fine too :) Whatever the easiest for you.
The actual VNC part I used comes from this guide: How to setup IBController on a headless Ubuntu
# install VNC server on remote Ubuntu (to access TWS GUI remotely)
apt install x11vnc
# run VNC server (note - it has 2 passwords: one for “view only” other for “full access with keyboard and mouse”):
/usr/bin/x11vnc -ncache 10 -ncache_cr -viewpasswd remote_view_only_pass -passwd some_pass123 -display :0 -forever -shared -logappend /var/log/x11vnc.log -bg -noipv6
...
# now we have ubuntu with GUI lets run TWS installer on display ‘0’:
cd ~/tws
DISPLAY=:0 ./tws-latest-standalone-linux-x64.sh
o/t having some fun getting the port forwarding to work (I presume - pinging the ib-controller host does not error when running under docker-compose), as per comment here: https://github.com/ib-controller/ib-controller/issues/109
do you guys actually have this working??
Would it be possible to get the output of this to tunnel through VNC ( like : https://github.com/clifton/docker-ib-gateway )
I haven't been able to get it working.