You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.
to initially setup the stack, one container will fail, usually setup_apm_server, with the following error:
setup_1 | setup_apm_server | Exiting: fail to create the Kibana loader: Error creating Kibana client: Error creating Kibana client: fail to get the Kibana version: HTTP GET request to /api/status fails: <nil>.
Response: {"statusCode":409,"error":"Conflict","message":"[doc][config:6.6.0]: version conflict, document already exists (current version [1]): [version_conflict_engine_exception] [doc][config:6.6.0]: version conflict, document already exists (current version ... (truncated).
Executing the standard docker-compose up -d to start the stack results in the stack being down, unable to login to Kibana at http://localhost:5601.
If the ELASTIC_PASSWORD env var is (re)set and setup is rerun for that service, e.g.:
docker-compose -f docker-compose.yml -f docker-compose.setup.yml up setup_apm_server
as per the setup.sh file, the container will complete, compose can be executed, and the stack can be pulled up.
This is running with no tags, the standard 6.6.0 currently used if the repo is cloned.
Running on:
ProductName: Mac OS X
ProductVersion: 10.14.1
BuildVersion: 18B75
Docker version 18.09.2, build 6247962
The text was updated successfully, but these errors were encountered:
Thank you sir! This worked well. We need a PR w/ this info for the README.md IMO as this was key for me on my MAC to get this working. I did the docker-compose with the two -f parameters above and then re-ran the docker-compose up -d again and voila!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When running
docker-compose -f setup.yml up
to initially setup the stack, one container will fail, usually
setup_apm_server
, with the following error:Executing the standard
docker-compose up -d
to start the stack results in the stack being down, unable to login to Kibana athttp://localhost:5601
.If the
ELASTIC_PASSWORD
env var is (re)set and setup is rerun for that service, e.g.:docker-compose -f docker-compose.yml -f docker-compose.setup.yml up setup_apm_server
as per the setup.sh file, the container will complete, compose can be executed, and the stack can be pulled up.
This is running with no tags, the standard 6.6.0 currently used if the repo is cloned.
Running on:
The text was updated successfully, but these errors were encountered: