Deployment Architecture

Splunk UF Docker Image root process writing splunkd's stderr.log to stdout

brent_weaver
Builder

Hello all... I am trying to use the docker container and it is starting a process under root that writes the splunkd stderr file to stdout, but as root:

 

 splunk tail -n 0 -f /opt/splunkforwarder/var/log/splunk/splunkd_stderr.log

 

How do I get that process to NOT start? We have a requirement that we cannot run processes as root in our containers. How do I either change the user running this process or stop it altogether? I get it that this means we will not get stderr.log files from the uf.

Any help is much appreciated.

Labels (1)
Tags (1)
0 Karma

kiragsplunk
Explorer

if you use splunk user as user account, please go ahead and change permission.

#chown -R splunk:splunk /opt/splunkforwarder

Hope this helps

0 Karma

brent_weaver
Builder
Spoiler
Hey thanks for the response. Splunk already running as splunk user and is owned by splunk. This seems to be a docker config that jobs off a tail of the log file.
0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...