From 83644d61ac12f6525865998acd344039cd56acef Mon Sep 17 00:00:00 2001 From: Craig P Steffen Date: Thu, 12 Dec 2024 12:13:51 -0600 Subject: [PATCH] ELK+UIUC_CM slightly works With this version of the docker-compose.yml, all the UIUC containers come up, and the two ELK containers come up as well. With this configuration I was able to log into the elasticsearch container and at least start the password setup utility. So I'm not going to say that it's *working*, but as far as elk is concnered it works at least as far as ELK ever has at NCSA. --- docker-compose.yml | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docker-compose.yml b/docker-compose.yml index 9898f83..5efaead 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -98,9 +98,9 @@ services: image: rabbitmq:3.13-management hostname: rabbitmq restart: unless-stopped - profiles: - - cdrhook - - allinone +# profiles: +# - cdrhook +# - allinone environment: RABBITMQ_DEFAULT_USER: "${RABBITMQ_USERNAME:-guest}" RABBITMQ_DEFAULT_PASS: "${RABBITMQ_PASSWORD:-guest}" @@ -115,16 +115,16 @@ services: image: ncsa/criticalmaas-cdr:${CDRHOOK_VERSION:-latest} hostname: cdrhook restart: unless-stopped - profiles: - - cdrhook - - allinone +# profiles: +# - cdrhook +# - allinone depends_on: - rabbitmq environment: # CDR_URL: "${CDR_URL}" CDR_TOKEN: "${CDR_TOKEN}" CDR_KEEP_EVENT: "no" - #CALLBACK_URL: "${CALLBACK_URL}" +# CALLBACK_URL: "${CALLBACK_URL}" CALLBACK_URL: "https://${SERVER_NAME}/cdr" CALLBACK_SECRET: "${CALLBACK_SECRET}" CALLBACK_USERNAME: "${CALLBACK_USERNAME}" @@ -145,9 +145,9 @@ services: hostname: monitor build: monitor restart: unless-stopped - profiles: - - cdrhook - - allinone +# profiles: +# - cdrhook +# - allinone depends_on: - rabbitmq environment: