-
Notifications
You must be signed in to change notification settings - Fork 102
Update to IB Gateway 978.2b and updates to deploy to Kubernetes using a Helm 3 chart #24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…tive Brokers Gateway and changes for it to be deployed in Kubernetes clusters using the ibgw HELM3 chart I have published.
…d before IB Gateway
Add Github action to build and test Docker container
…e starting socat instead of using sleep 30
Add build and push Docker workflow
Delete docker-image.yml
I personally don't need kubernetes, but the main problem I'm trying to solve is make the container more stable / auto restart on exceptions. Right now, I have to kill and remove the docker container and recreate it at least once every day, sometimes more often. Will these changes fix this? Is there a smaller subset of these changes that would fix it, ie. the few lines changed in the runscript.sh alone? Thanks very much! |
I'm trying to refactor further to not need socat to redirect to localhost. Socat redirect seems to be resulting in some performance slowdowns and disconnects. Updating the ibg.xml to allow connections not just from localhost should do this, but ibg.xml gets placed in the directory that is created after startup. https://github.com/ajpierce/ib_tws_docker is another Dockerization of IBG that tries to use ibg.xml, but it seems to be currently set up for their specific user, and they create that by starting, killing, and then restarting IBGW which seems very inefficient. I have been using Kubernetes to monitor and restart IBGW, but there's more refinement that can be done, such as watching for the timestamp, account information, or tick data to ensure it is fully active. The allowOnlyLocalhost value below is what needs to be changed.
|
…d to IBC3.8.4-beta.2 from IBController.
…t with the path update now in the helm chart. Move to start socat first, IB Gateway start last so it should exit the pod if it crashes.
… fully responding
Update startup
I'm still watching! Feel free to ping me when you think this is at a stopping point |
Thanks, I'm still working on a lot of little quirks and issues. It seems like xvfb-run is not reliably starting, so I'm going to try changing to tigervnc-standalone-server. IBGW has stopped responding to API requests, until I change to another port and back, then it starts working again. I want this to be very stable, so it can be used for reliable trading. |
Change xvnc
…r update to remove anything from /tmp on boot.
I have created this update to download and install the current stable release of Interactive Brokers Gateway v978.2b. I have also updated the runscript to get rid of socat and use the IB Gateway port directly to reduce overhead and to enable deploying this image to Kubernetes with TCP port monitoring and automatic restart when the port is unavailable.
I also created a Helm 3 chart to deploy to Kubernetes at https://github.com/forhire/ibgw to make Kubernetes deployment easy, using Kubernetes secrets to store credentials.