-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
"No Available connections" container vs host #16099
Comments
In the |
@mashhurs awesome! Thank you, it didn't dawn on me to compare the default configuration. I was hung up on the |
Got it working. Just for anyone else (who is green on all the various settings). I had to use
Thank you once more @mashhurs |
Logstash information:
Please include the following information:
docker pull logstash:8.13.0
Plugins installed: (
bin/logstash-plugin list --verbose
)JVM (e.g.
java -version
):container
OS version (
uname -a
if on a Unix-like system):Description of the problem including expected versus actual behavior:
Its seems logstash makes a connection (once) but then loses it. It is like host.docker.internal is there but then reloads the config and fails parsing and falls back to output elasticsearch? (just a hunch).
If I run ES in a container (docker desktop on mac) and instead run logstash with the exact same config it works (see below).
Steps to reproduce:
On MacBook
docker container run -d --name elasticsearch -p 9200:9200 -m 1GB elasticsearch:8.13.0
docker container run -d --name kibana -p 5601:5601 kibana:8.13.0
Provide logs (if relevant):
Here is where I run logstash on the host instead of a container (elasticsearch is in a container still though).
In either case, I hit logstash with curl
Its probably my setup, but just seeing the issue.
The text was updated successfully, but these errors were encountered: