-
Notifications
You must be signed in to change notification settings - Fork 27
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
nc: bad address 'elasticsearch' #3
Comments
hmm, did you miss the create network step? |
No, though I did leave it out in my script above. Edited to fix. Here's what happens when I try again:
|
Unfortunately no. I haven't been able to make any more progress. I might try again tonight using Ubuntu in case there's some distribution differences that impact things. |
Cool, I sent an email 👍 |
What version of docker are you running, and could you send your |
also get same error installed on ubuntu 16.04 with latest docker-ce |
looks like this error occurs as ES fails to start
|
this is due to the local volume mapped to however getting memory issues with ES after this..
|
Exactly, those are common issues when running Elasticsearch containers. The owner needs to be set to UID 1000 (this is the docker default user) and vm.max_map_count needs to be increased. |
@psifertex the nc: bad address 'elasticsearch' is almost certainly because ES has failed to start. |
|
The VM I created only had 1GB ram total. Oh, looking through the config:
So yeah, that won't work. Apparently no swap by default either. Any reason performance would really be an issue for an instance only logging one slack? I might just crank down the java heap size and try that. (AWS does have dedicated ES instances I could pop up as well that appear to run with 1gb of ram but then I'd have to re-configure the config to use that) |
yeah Elastic recommend 4Gb ram for ES 5.x but it will run on less, but 1Gb I think way too small, especially if you running mongo and other containers on same instance |
AWS itself has a |
I'm getting this issue now as well... Also using 2cpu 4gb ram. |
This is I am getting running |
Just solved it with |
When trying to
docker-compose run
according to the initial instruction setup.I even tried adding elasticsearch to
/etc/hosts
for 127.0.0.1, but that didn't help either. Looks like it's actually a setting from within one of the instances?For reference, I took a fresh AWS EC Linux 2 instance and:
The text was updated successfully, but these errors were encountered: