Docker Container: TWS won't start

[Jinzuu]

I am trying to run thetagang's docker image.

However, when executing the docker run command, it just sits at this point and does nothing:

Exchange Hours XFRA
────────────────────────────────────────────
Open 2025-07-04 07:00:00+00:00
Close 2025-07-04 15:30:00+00:00
Start 2025-07-04 07:30:00+00:00
End 2025-07-04 15:00:00+00:00

Starting TWS with twsVersion=1030

At this point, nothing else happens. I let it sit for some time (minutes) but nothing happens.

In the ib_async log it reads:

2025-07-04 08:27:51,708 ib_async.client INFO Connecting to 127.0.0.1:7497 with clientId 1...
2025-07-04 08:27:51,710 ib_async.client INFO Disconnecting
2025-07-04 08:27:51,710 ib_async.client ERROR API connection failed: ConnectionRefusedError(111, "Connect call failed ('127.0.0.1', 7497)")
2025-07-04 08:27:51,711 ib_async.client ERROR Make sure API port on TWS/IBG is open

Does the thetagang-docker need anything else? I thought IBC and TWS is contained in the docker container?

[brndnmtthws]

Can you run TWS without thetagang? My guess is it's waiting on 2FA.

[Jinzuu]

How do I do that? TWS is included in the Container is it not, and the entrypoint in the container is fixed through the Dockerfile.
So I don't know how I should manually start the TWS inside the docker container.

If TWS is not included in the container, then the structure (and the contents) of the container is unclear to me.
Can you elaborate on the structure and interplay of TWS/Gateway, IBC, ib_async and thetagang-application?

[brndnmtthws]

No, I mean run the application normally on your computer without docker/thetagang in any way. The readme has instructions on how to deal with the 2FA issue under "IBKey and MFA-related authentication issues".

[Jinzuu]

The application runs normally. I trade everyday without problems.
In addition, I have IBC installed locally and I am able to start both, TWS and the Gateway, through IBC.
So that works without problems.

[Jinzuu]

I just went through the Docker file again to make sure I didn't miss anything.

So as far as I can tell, TWS is included in the container. So there shouldn't be any outside requirements in terms of libs or applications, right?

Is there any way to enable a verbose debug output in the container so that I can pinpoint more exactly where it hangs?

[Jinzuu]

I made progress. The entry point script in the container starts Xvfb and uses that output.
I am running docker on windows and so I didn't see anything.
I overrode the entry point, installed an X server in my system and set DISPLAY to host.docker.internal:0 and now TWS starts.

Problem is now that I can't persistently change the entry point script because I can't build the docker Container from scratch as I don't have all the files which are ADDed in the script available.

Would it make sense to extend the container in such a way that the display configuration can be configured from outside?

Im happy to help myself but for that I would need all the files to build and as far as I can see, TWS is missing in the build system.

[robby28-11]

No changes on my side and suddenly I'm getting the same error. Was working without issues for month.