Getting Data In

Proper way to mount configs in Splunk Docker Container

cloutid
New Member

Hello, currently working on Spinning up Splunk Containers using the splunk latest image. Works great when using all defaults but when I try and bind mount some of my existing configs that I wish to use, it seems the files are either getting locked or not being used.

For example, for the splunk db connect app my connection information appears but states it's invalid? and when copied manually over to the container, it works. i've pinned it down to the identities.conf file that is causing the issue, perhaps there is a better way to bring config files over when spinning up the container.

Another example is just copying MIBS files seems has no effect but works when copied manually...

Thanks!

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...