Ibg-1 websockify error

Technical Help
#1

Hi Brian,

It seems that since the latest update of the MacOS to 14.4.1 I am getting the below error from ibg-1 container. I have tried recreating all the containers but the error does not seem to go away.

Any insights as to what is causing this? It is also eating CPU time in the background at a rate of 8% .

I am also running Docker Desktop 4.29.0 (145265)

Thanks

Container log output.
2024-04-08 13:18:09 subprocess 1787 exited with code 1
2024-04-08 13:18:38 Starting websockify.
2024-04-08 13:18:39 subprocess 1806 exited with code 1
2024-04-08 13:19:08 Starting websockify.
2024-04-08 13:19:09 subprocess 1825 exited with code 1
2024-04-08 13:19:38 Starting websockify.
2024-04-08 13:19:39 subprocess 1844 exited with code 1
2024-04-08 13:20:09 Starting websockify.
2024-04-08 13:20:10 subprocess 1863 exited with code 1
2024-04-08 13:20:39 Starting websockify.
2024-04-08 13:20:40 subprocess 1882 exited with code 1

Flight Log file output.
2024-04-08 20:16:06 quantrocket.ibg1: WARNING websockify still not running after 30 seconds, starting again
2024-04-08 20:16:37 quantrocket.ibg1: WARNING websockify still not running after 30 seconds, starting again

quantrocket-ibg1-1|Starting websockify.
quantrocket-flightlog-1|2024-04-08 20:24:41 quantrocket.ibg1: WARNING websockify still not running after 30 seconds, starting again

    quantrocket-houston-1|172.18.0.11 - - [08/Apr/2024:20:25:06 +0000] "GET /ibg1/gateway HTTP/1.1" 200 22 "-" "python-requests/2.27.1"
    quantrocket-houston-1|172.18.0.13 - - [08/Apr/2024:20:25:06 +0000] "GET /ibgrouter/gateways?status=running HTTP/1.1" 200 3 "-" "python-urllib3/1.26.8"
       quantrocket-ibg1-1|Starting websockify.
  quantrocket-flightlog-1|2024-04-08 20:25:11 quantrocket.ibg1: WARNING websockify still not running after 30 seconds, starting again
#2

The ibg container runs under emulation on Apple Silicon, and while I haven't seen running under emulation cause that particular error, it could be related. There's more info about the limitations of running the ibg container on Apple Silicon in the Mac installation tutorial.

Since you're seeing noisy logs and CPU usage, I would just stop and remove the ibg1 container:

docker compose stop ibg1
docker compose rm ibg1

If you need to connect to IBKR, I recommend doing that on an Intel machine and copying data over to Apple Silicon, as discussed in the above link.