Prevent external service localhost question #497
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Every time a potential user of AnythingLLM uses AnythingLLM in a dockerized context there is confusion on why some external service running on localhost/loopback [LocalAi, LMStudio, Ollama, Chroma, etc] cannot connect, resulting in failed messages or other problems during use.
This is because localhost or loopback IPs resolve within the AnythingLLM container while the service they wish to connect to uses the host machine network. The full fix is to simply replace
localhostor127.0.0.1withhost.docker.internaland the container can then reach the host machine network.This is already outlined in the Docker README as an important tag, but considering some may be pulling from remote and never consulting the README this detail gets missed nearly all the time.
This PR blocks localhost or 127.0.0.1 from being used for external services while running inside of Docker.
Hopefully, we never have to answer this question again 😵