We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug When trying to run the gateway it fails to start the container
To Reproduce set
TWS_USERID TWS_PASSWORD TRADING_MODE READ_ONLY_API
run docker-compose up
docker-compose up
Expected behavior The gateway container to run
Container logs Error message, it tries to run again after about 15 seconds and faces the same issue
ib-gateway-1 | 2024-02-07 10:46:55:461 IBC: Using default settings provider: ini file is /root/ibc/config.ini ib-gateway-1 | 2024-02-07 10:46:55:462 IBC: Using default login manager: getting username and password from args ib-gateway-1 | 2024-02-07 10:46:55:462 IBC: Using default main window manager ib-gateway-1 | 2024-02-07 10:46:55:462 IBC: Using default trading mode manager: constructor parameter args: tradingMode=paper ib-gateway-1 | 2024-02-07 10:46:55:464 IBC: Using default config dialog manager ib-gateway-1 | 2024-02-07 10:46:55:468 IBC: CommandServer is not started because the port is not configured ib-gateway-1 | 2024-02-07 10:46:55:569 IBC: TWS Settings directory is: /root/Jts ib-gateway-1 | 2024-02-07 10:46:55:574 IBC: Ensuring /root/Jts/jts.ini contains required minimal lines ib-gateway-1 | 2024-02-07 10:46:55:575 IBC: Found setting: [Logon]/s3store=true ib-gateway-1 | 2024-02-07 10:46:55:575 IBC: Found setting: [Logon]/Locale=en ib-gateway-1 | 2024-02-07 10:46:55:575 IBC: Found setting: [Logon]/displayedproxymsg=1 ib-gateway-1 | 2024-02-07 10:46:55:575 IBC: Found setting: [Logon]/UseSSL=true ib-gateway-1 | 2024-02-07 10:46:55:575 IBC: Found setting: [IBGateway]/ApiOnly=true ib-gateway-1 | 2024-02-07 10:46:55:575 IBC: Confirmed /root/Jts/jts.ini contains required minimal lines ib-gateway-1 | 2024-02-07 10:46:55:575 IBC: Starting Gateway ib-gateway-1 | 2024-02-07 10:46:55:575 IBC: Starting session: will exit if login dialog is not displayed within 60 seconds ib-gateway-1 | assertion failed [rem_idx != -1]: Unable to find existing allocation for shared memory segment to unmap ib-gateway-1 | (VMAllocationTracker.cpp:745 remove_shared_mem) ib-gateway-1 | /root/ibc/scripts/ibcstart.sh: line 468: 125 Trace/breakpoint trap "$java_path/java" -cp "$ibc_classpath" $java_vm_options$autorestart_option $entry_point "$ibc_ini" "$ib_user_id" "$ib_password" ${mode} ib-gateway-1 | IBC returned exit status 133 ib-gateway-1 | Renaming TWS or Gateway .exe file to original name ib-gateway-1 | ib-gateway-1 | Gateway finished ib-gateway-1 | ib-gateway-1 exited with code 133
Versions (please complete the following information):
docker --version
docker images --digests
The text was updated successfully, but these errors were encountered:
I have the exact same issue with M1 as well...
Sorry, something went wrong.
I have same issue, does anyone know how to fix that?
same here
No branches or pull requests
Describe the bug
When trying to run the gateway it fails to start the container
To Reproduce
set
run
docker-compose up
Expected behavior
The gateway container to run
Container logs
Error message, it tries to run again after about 15 seconds and faces the same issue
Versions (please complete the following information):
docker --version
): latestdocker images --digests
): sha256:5f3311ed8dab171e5f955fdeca15ca269cea899577b82ad5955c5956e13461c3The text was updated successfully, but these errors were encountered: