"No private IP address found, and explicit IP not provided" when spinning Weaviate on Azure App Service #4
Description
First of all - great project 👏👏👏
I am trying to spin embedded instance on Azure App Service and I am getting following:
connected to embedded db!
Embedded db already listening @ 127.0.0.1:8080
Started /root/.cache/weaviate-embedded-1.19.8 @ 127.0.0.1:8080 -- process ID 313
{"action":"startup","default_vectorizer_module":"img2vec-neural","level":"info","msg":"the default vectorizer modules is set to \"img2vec-neural\", as a result all new schema classes without an explicit vectorizer setting, will use this vectorizer","time":"2023-06-23T19:25:51Z"}
{"action":"startup","auto_schema_enabled":true,"level":"info","msg":"auto schema enabled setting is set to \"true\"","time":"2023-06-23T19:25:51Z"}
{"action":"memberlist_init","bind_port":43599,"error":"Failed to get final advertise address: No private IP address found, and explicit IP not provided","hostname":"Embedded_at_8080","level":"error","msg":"memberlist not created","time":"2023-06-23T19:25:51Z"}
{"action":"startup","error":"create member list: Failed to get final advertise address: No private IP address found, and explicit IP not provided","level":"error","msg":"could not init cluster state","time":"2023-06-23T19:25:51Z"}
connected to embedded db!
And that's my setup:
const client: EmbeddedClient = await weaviate.client(
new EmbeddedOptions({
port: 8080,
env: {
DEFAULT_VECTORIZER_MODULE: "img2vec-neural",
ENABLE_MODULES: "img2vec-neural",
},
version: "1.19.8",
})
);
await client.embedded.start();So despite that it's logging connected to embedded db! I can't do anything with the database. For example, an attempt to get schema:
const schemaRes = await client.schema.getter().do();
Results in:
Error: usage error (404): <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>Cannot GET /v1/schema</pre>
</body>
</html>But if I understand correctly embedded instance is not starting due to problem with private IP address.
I'm not sure if this is not an environment specific problem. If so - I am happy to provide any details that might help making Weaviate Azure App Service friendly.