Welcome to Splunk Answers, a Q&A forum for users to find answers to questions about deploying, managing, and using Splunk products. Contributors of all backgrounds and levels of expertise come here to find solutions to their issues, and to help other users in the Splunk community with their own questions.

This quick tutorial will help you get started with key features to help you find the answers you need. You will receive 10 karma points upon successful completion!

Refine your search:

Docker Config option for Splunk web.conf error

1

I am using Splunk/splunk:latest version(7.0.0) and docker compose version (3.4) .Also deploying an nginx proxy with context root as /splunk to forward to splunk web at 8000.

The web.conf is added to the container as a docker config at /opt/splunk/etc/system/local/web.conf as root user, and also starting the container as root user.The splunk container fails to start with error: chown: changing ownership of ‘/opt/splunk/etc/system/local/web.conf’: Read-only file system

People who like this

I am running the latest docker image and have a similar issue. Running 7.0.2 on Docker CE with Portainer.The user and group defined by the default variables are splunk splunkHowever when I check the files in the /etc volume they are all owned by docker with the exception of modified files which become owned by root.

1 Answer

I am running the latest docker image and have a similar issue. Running 7.0.2 on Docker CE with Portainer.The user and group defined by the default variables are splunk splunkHowever when I check the files in the /etc volume they are all owned by docker with the exception of modified files which become owned by root.