splunk / splunk/docker-splunk

cluster_absolute_unit.yaml doesnt run as advertised

Open
#724 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
549
Forks
277
Avg merge
3d 9h
Merged PRs (30d)
2

Description

Following the this documentation:
https://splunk.github.io/docker-splunk/advanced/DISTRIBUTED_TOPOLOGY.html

I wasnt able to start the cluster up.
Issues faced:

  1. default.yml inside ./test_scenarios/defaults/ wasnt respected atleast not for the password (generated via docker run with "SPLUNK_PASSWORD" set
  2. did not read the set env-var SPLUNK_PASSWORD when running compose up via make (also not when setting environment:
    - SPLUNK_PASSWORD (which is missing in this compose file)
  3. Required adding - SPLUNK_GENERAL_TERMS=--accept-sgt-current-at-splunk-com otherwise I would get license not accepted error.

How i generated default.yml:
docker run -it -e SPLUNK_PASSWORD=savepassword splunk/splunk:latest create-defaults > test_scenarios/defaults/default.yml

How I started the containers:
SPLUNK_PASSWORD=savepassword ; SPLUNK_COMPOSE=cluster_absolute_unit.yaml make sample-compose-up

OS: MacOS ARM64 (latest)
Docker Desktop: Version 4.45.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the DISTRIBUTED_TOPOLOGY documentation and the cluster_absolute_unit.yaml scenario, then inspect test_scenarios/defaults/default.yml and the sample-compose-up Make target. Reproduce the commands and check how SPLUNK_PASSWORD and SPLUNK_GENERAL_TERMS are passed into Compose. Done means the documented startup works with the generated defaults and required environment values, including license acceptance.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose
Domain
devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.