IBGA is not pinned to a specific version of IB Gateway

[jpike88]

This is a possible explanation of why my last two issues happened. It's possible that the scripts are simply not aligning with the latest version of IB Gateway.

It's very difficult for me to verify this as I do not know the last version that actually worked. Do you use IBG_DOWNLOAD_URL and pin a specific version, if so, what version is it?

ibga/scripts/_env.sh

Line 9 in 9925b60

DEFAULT_URL="https://download2.interactivebrokers.com/installers/ibgateway/latest-standalone/ibgateway-latest-standalone-linux-arm.sh"

[jpike88]

Nope... using IBG_DOWNLOAD_URL=https://download2.interactivebrokers.com/installers/ibgateway/stable-standalone/ibgateway-stable-standalone-linux-arm.sh didn't help either. The logs show that it downloaded the stable script, but no success past that point (same problems are happening).

[heshiming]

I'll debug the code against the other issues you found. Chances are a recent update changed things.

Although, this project is a workaround for the problem of "automatically start IBG and keep it up". I can't pin it to a specific version because IBKR doesn't allow download of a specific version. Sooner or later it'll hit an issue with the update and the only fix would be to deal with the changes.

I don't update IBG very often myself.

[jpike88]

I was trying https://github.com/gnzsnz/ib-gateway-docker/tree/master before this one, and in that repo they supply pinned versions of IB Gateway/TWS. Maybe like you they can't control which version they get at, they just get the latest and work with it.

https://github.com/gnzsnz/ib-gateway-docker/tree/master#supported-tags

Isn't it a far safer approach to just roll an image with the latest version already installed, and test your scripts with that? I understand once it makes it to production it may not be updated much, but that uncertainty introduces some serious risk, does it not?