You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why not just use a generic container for this?
If using DockerContaine("trinodb/trino:latest"), the get_exposed_port with @wait_container_is_ready() will be stuck until 120s timeout.
The Trino docker image does not default expose the port. We need to bind the port explicitly.
And it should check .*======== SERVER STARTED ========.* and execute a statement to trigger the node register like below.
What is the new container you'd like to have?
Trino
Official website: https://trino.io
Github: https://github.com/trinodb/trino
Docker hub: https://hub.docker.com/r/trinodb/trino
Why not just use a generic container for this?
If using
DockerContaine("trinodb/trino:latest")
, theget_exposed_port
with@wait_container_is_ready()
will be stuck until 120s timeout.The Trino docker image does not default expose the port. We need to bind the port explicitly.
And it should check
.*======== SERVER STARTED ========.*
and execute a statement to trigger the node register like below.Other references:
Follow #152
I already created a
TrinoContainer
in project wren-engine. If you agreed, I can add a pull request to implement this issue.The text was updated successfully, but these errors were encountered: