-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SolrTest failure when using CloundContainer #2967
Comments
Eventually I find a way to fix this. And this discussion docker-solr/docker-solr-examples#5 inspired |
ffang
added a commit
to ffang/camel-quarkus
that referenced
this issue
Aug 20, 2021
ffang
added a commit
to ffang/camel-quarkus
that referenced
this issue
Aug 24, 2021
ppalaga
pushed a commit
that referenced
this issue
Aug 26, 2021
ppalaga
pushed a commit
that referenced
this issue
Aug 26, 2021
ppalaga
added a commit
to ppalaga/camel-quarkus
that referenced
this issue
Aug 26, 2021
…- do not assume the class path resource is accessible via filesystem
ppalaga
added a commit
that referenced
this issue
Aug 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This probably only is the problem on non-linux machines.
I got test failures on my Mac when using CloundContainer(SSLContainer and StandaloneContainer are good though)
the error is like
Notice that 172.30.0.4 is the virtual docker node ip, but on non-linux machines with Docker Desktop, we can't access the virtual docker node ip.
This 172.30.0.4 was passed in org.apache.solr.client.solrj.impl.BaseCloudSolrClient by
So if we can find a way(like in cloud-docker-compose.yml configuration) to pass in the well-known hostname "host.docker.internal" on Docker Desktop as the replica nodename, we should be able to make it work.
The text was updated successfully, but these errors were encountered: