<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Splunk UF Docker Image root process writing splunkd's stderr.log  to stdout in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-UF-Docker-Image-root-process-writing-splunkd-s-stderr-log/m-p/532005#M18298</link>
    <description>&lt;LI-SPOILER&gt;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.&lt;/LI-SPOILER&gt;</description>
    <pubDate>Fri, 04 Dec 2020 12:00:31 GMT</pubDate>
    <dc:creator>brent_weaver</dc:creator>
    <dc:date>2020-12-04T12:00:31Z</dc:date>
    <item>
      <title>Splunk UF Docker Image root process writing splunkd's stderr.log  to stdout</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-UF-Docker-Image-root-process-writing-splunkd-s-stderr-log/m-p/531943#M18296</link>
      <description>&lt;P&gt;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:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt; splunk tail -n 0 -f /opt/splunkforwarder/var/log/splunk/splunkd_stderr.log&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;Any help is much appreciated.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Dec 2020 01:27:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-UF-Docker-Image-root-process-writing-splunkd-s-stderr-log/m-p/531943#M18296</guid>
      <dc:creator>brent_weaver</dc:creator>
      <dc:date>2020-12-04T01:27:35Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk UF Docker Image root process writing splunkd's stderr.log  to stdout</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-UF-Docker-Image-root-process-writing-splunkd-s-stderr-log/m-p/531945#M18297</link>
      <description>&lt;P&gt;if you use splunk user as user account, please go ahead and change permission.&lt;BR /&gt;&lt;BR /&gt;#chown -R splunk:splunk /opt/splunkforwarder&lt;BR /&gt;&lt;BR /&gt;Hope this helps&lt;/P&gt;</description>
      <pubDate>Fri, 04 Dec 2020 01:33:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-UF-Docker-Image-root-process-writing-splunkd-s-stderr-log/m-p/531945#M18297</guid>
      <dc:creator>kiragsplunk</dc:creator>
      <dc:date>2020-12-04T01:33:53Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk UF Docker Image root process writing splunkd's stderr.log  to stdout</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-UF-Docker-Image-root-process-writing-splunkd-s-stderr-log/m-p/532005#M18298</link>
      <description>&lt;LI-SPOILER&gt;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.&lt;/LI-SPOILER&gt;</description>
      <pubDate>Fri, 04 Dec 2020 12:00:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-UF-Docker-Image-root-process-writing-splunkd-s-stderr-log/m-p/532005#M18298</guid>
      <dc:creator>brent_weaver</dc:creator>
      <dc:date>2020-12-04T12:00:31Z</dc:date>
    </item>
  </channel>
</rss>

