log4j link broken
iamthebot opened this issue · comments
Build fails due to wget not being able to pull log4j. Not sure how to find what version we should be using now?
Looking into this. Thanks for reporting
Tried using a generally available version of log4j but there appears to be an issue with the jars used from ib's site. I'll look into it further when I have time.
Hmm, seems like the jars referenced in #3 aren't working any longer. @buzzcloudau, are you still using this container? If so, any chance you could update this?
In the meantime, you could try using the latest working build off of docker hub or try @castedo's alternative, brokertron
@clifton I'm not really using this container either (just needed it for FIX certification, we connect with a more direct method in production). Brokertron works for the TWS API but didn't work with FIX for whatever reason. Will leave this issue open in case anybody comes up with a way to pull the correct links.
Ah, okay. I'll circle back and fix this next time I need to pull from TWS programmatically.
Sorry, I moved on to installing the IB Gateway directly on the server. Im not using any Docker instances any more.
If it helps, this is my setup script for installing two instances of IB and IB Controller (main account and a paper account.)
It is mostly based on this project and the IB Controller help guide.