splunk / splunk/docker-splunk

SPLUNK_DEPLOYMENT_SERVER Environment variable is not used/considered

Open
#555 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

Splunk Version: Latest (9.0.0)
As mentioned here: https://splunk.github.io/docker-splunk/EXAMPLES.html
the SPLUNK_DEPLOYMENT_SERVER variable is not used or considered in the startup
Event the entrypoint.sh is not listing this.
after pulling splunk latest we create and run as follows:

docker run --name splunk-uf -h $HOSTNAME -e "SPLUNK_PASSWORD=MySecurePassword" -e "SPLUNK_START_ARGS=--accept-license" -e "SPLUNK_DEPLOYMENT_SERVER=192.168.12.3:8089" -d splunk/splunk:latest
After a while this is the command what we run:
docker exec -u root splunk-uf /opt/splunk/bin/splunk show deploy-poll -auth "admin:MySecurePassword" WARNING: Server Certificate Hostname Validation is disabled. Please see server.conf/[sslConfig]/cliVerifyServerName for details. Deployment Server URI is not set.

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 by reading entrypoint.sh and the deployment-server example linked in the issue to trace how startup environment variables are handled. Reproduce the Docker command, then verify with splunk show deploy-poll that SPLUNK_DEPLOYMENT_SERVER is configured and reported as the deployment server.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.