Closed kosarko closed 3 years ago
On Linux, host.docker.internal resolves to nothing. See the following docker open issue: docker/for-linux#264 . Looking for other solution.
yes, host.docker.internal
is windows only I think. The solution should be to run both containers in the same docker network (either the default, or one specially created for them); then one could just use the container name.
When using a compose file (https://docs.docker.com/compose/); it creates a network for the configured services.
edit: assuming wembedding is also running in a container
Yes, that's what I did in the end: both containers (NameTag2 and WEmbeddings) run in separate containers, connecting to specially created network for communication. It's already described in README.
There are more details in the commit messages