Hi @balaji.ramaswamy,
Let me clarify my current configuration. My Dremio instance is now running remotely at, say, ip address 52.123.456.789
My Metabase client which has the Dremio JDBC driver installed is running in a docker container.
The connection string I have been using (as well as trying many other permutations) in the container is:
jdbc:dremio:direct=127.0.0.1:31010
When you speak of “dremio-coordinator-docker” I am assuming you are referring to the Dremio instance running at 52.123.456.789
Is this assumption correct? I am not too knowledgeable about what a Dremio Coordinator is, or how it is different from the Dremio Executor service, or if they are on separate ip addresses.
So when you say “telnet dremio-coordinator-docker 31010” I would run:
docker exec -it metabase telnet 52.123.456.789 31010
and then I get:
rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:262: starting container process caused “exec: “telnet”: executable file not found in $PATH”
When I ran “telnet 52.123.456.789 31010” it was ran from my local host machine, not the container.
And that’s where I got:
Trying 52.123.456.789…
Connected to 52.123.456.789.
Escape character is ‘^]’.
Connection closed by foreign host.
So does that mean that the Dremio port 31010 at 52.123.456.789 is open and my docker container should be able to access it?
Does that mean that the problem is with the connectivity from my container?
When I run either “docker exec -it metabase telnet localhost 31010” or “docker exec -it metabase telnet 127.0.0.1 31010”, I get:
rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:262: starting container process caused “exec: “telnet”: executable file not found in $PATH”
Does this mean that the problem is that my container cannot access port 31010 on the local host?
What must I do?