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
We identified a bug in the indexing pipeline, which appears to be confined to a specific docker and linux version. To address this issue, when encountering a similar problem, follow these steps to resolve the bug:
When running the index_weaviate component with the local runner, there may be issues connecting to a local weaviate instance. To resolve this, note that we typically use http://host.docker.internal to determine the correct address of the database. However, in the specific setup where the issue arises, the host name is not recognised in the operating system.
In such cases, a workaround is to use the IP address 172.17.0.1 directly instead of relying on http://host.docker.internal to ensure successful connectivity.
We identified a bug in the indexing pipeline, which appears to be confined to a specific docker and linux version. To address this issue, when encountering a similar problem, follow these steps to resolve the bug:
When running the
index_weaviate
component with the local runner, there may be issues connecting to a local weaviate instance. To resolve this, note that we typically usehttp://host.docker.internal
to determine the correct address of the database. However, in the specific setup where the issue arises, the host name is not recognised in the operating system.In such cases, a workaround is to use the IP address
172.17.0.1
directly instead of relying onhttp://host.docker.internal
to ensure successful connectivity.Docker version: Docker version 20.10.17, build 100c701
OS: Debian GNU/Linux 11 (bullseye)
The text was updated successfully, but these errors were encountered: