gresockj commented on PR #6658: URL: https://github.com/apache/nifi/pull/6658#issuecomment-1427007337
> Going back to the earlier Docker question - is it that you're running Elasticsearch as a Docker container but NiFi "natively" on your machine, connecting to Elasticsearch using `localhost` and then the Elasticsearch instance is reporting back the Docker-internal address of `172.17.0.3`? What do you see under the `http` section of the response from a call to your Elasticsearch's `GET /_nodes/http` API? Yes, that is my setup, and I get similar output to what you posted. > which isn't contactable from my browser/terminal - so I suspect this is indeed what's going on for you, i.e. your Elasticsearch instance is reporting back its "internal" IP as its `publish_address` and you'd need to re-configure the instance's `network.publish_address` (or run NiFi within the Docker network **or** use the `host` network for your Elasticsearch container) so that the correct combination of `publish_address` and host network routing can be used Good catch -- when I added `-e network.publish_host=192.168.1.X` to my docker run command, and used the same IP in the NiFi ES client service, the sniffer worked correctly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
