I’ve only had a little time to look into this. This is all I’ve found so far:
Using the IP address instead of the FQDN resolves the issue (in a sense)
Using the FQDN or just the hostname both fail, although they both ping and work otherwise in the container
Using the FQDN or just the hostname both successfully ‘Cluster.connect’. That is, no error is produced. However, when I use a non-resolvable name, Cluster.connect does throw an exception.
I spent some time tracing the flow of execution. It comes down to a call to an _http_request function that looks like a C call back into libcouchbase. I’m having difficulty finding the actual function, looking both in the libcouchbase github and the python-sdk github. The class “couchbase.management.Admin” is created from the class LCB.Bucket, which comes from couchbase_core._libcouchbase – searching for “Bucket” in there is, as you can imagine, getting a lot of hits.
Do you know where I can find the code for Bucket or ultimately Bucket._http_request? I’m hoping that may expose what’s happening here. The problem, I"m sure is something in the docker setup, but I need to know how to reproduce the issue outside of couchbase to figure out the problem.
In the meantime, I just use the IP address to connect – but this is not a great solution.
Thanks for your help!
-Eric