Do not re-install splunk when restarting the container
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- ansible, docker
- Domain
- devops, infrastructure
Research direction
The issue identifies the container startup path and Ansible playbook as the relevant entry points; begin by tracing how startup decides to run the playbook on each launch. Test a fresh container and then a stop/start cycle, and consider the work complete when an installed instance starts without reinstalling while a fresh instance still performs the installation.
Written by the indexing model from the issue text.
Description
Is there an option to prevent the container from re-running the ansible playbook that reinstalls everything when the container starts for the second time?
Context: We use https://github.com/splunk/contentctl to do detection engineering in splunk, and we test the rules locally on our machine, and we spin up a splunk instance which takes a little less than 20 minutes to fully install everything needed. Once installed, we don't need to re-install everything to test a new set of rules. But every time we shut down the container, we need to wait 20 minutes just to re-install everything for no benefit
- Dominant language
- Python
- Stars
- 549
- Forks
- 278
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from splunk/docker-splunk
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
splunk/docker-splunk#730 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
splunk/docker-splunk#737 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
splunk/docker-splunk#732 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
splunk/docker-splunk#731 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
splunk/docker-splunk#724 ·
All issues in splunk/docker-splunk
Similar issues
-
camlight produces degenerate target camera and light framesPossibly taken @kavyabhand claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google-deepmind/mujoco_warp#1743 ·
Maintainers usually reply within 1 day
-
Package: Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
getsolus/packages#10933 · 1 comment ·
Maintainers usually reply within 1 day
-
[work-item] adam-adae-serious-events: pin missing-AESER filter semanticsPossibly taken @muse-yamaa-bot claimed this today. Openwork-item
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
[Bug]: Non-vision image fallback calls vision_analyze with an empty source for oversized inline images and tells the model the image is corruptPossibly taken @liuhao1024 claimed this today. Opencomp/agent P2 tool/vision type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#132605 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pymc-labs/pymc-marketing#3102 · 1 comment ·
Maintainers usually reply within 1 day