Splunk support driver#

Docker does not start if the daemon.json file contains badly-formed JSON. Note: If you already have an existing JSON file, add only 'storage-driver': 'overlay2' as a key-value pair. Assuming the file was empty, add the following contents:.

Splunk support driver#

OverlayFS overlay2 Docker daemon storage driver.It’s possible that this Docker image still works, although you may need to manually add the environment variable KUBERNETES_SERVICE_HOST=kubernetes to configure the provisioning hooks properly. Note: If you are using podman, CRI-O, containerd or other container runtimes, please be aware that these are currently outside of our support/testing matrix. Docker Enterprise Engine 17.06.2 or higherĭocker Community Engine 17.06.2 or higher.splunk/universalforwarder image supports both x86-64 and s390x chipsets.splunk/splunk image supports x86-64 chipsets.Linux-based operating system, such as Debian, CentOS, and so on.The following prerequisites and dependencies must be installed on each node you plan on deploying the container. Failure to do so will render your deployment in an unsupported state. If you intend for this containerized Splunk Enterprise deployment to be supported in your Enterprise Support Agreement, you must verify you meet all of the requirements below. Throughout this document, the term “supported” means you can contact Splunk Support for assistance with issues. However, because not all settings apply to all customers, Splunk will only support the most common subset of all configurations.

Splunk Enterprise contains many settings that allow customers to tailor their Splunk environment.