Splunk Dev

Logging Driver is Always loading file from the system

eygtmbot
Engager

Hello,
I'm trying to install splunk logging driver on my swarm master. Here is the stack file I'm using

version: '3'
services:
  web:
    image: "${DOCKER_IMAGE_PATH}/:${RELEASE_TAG}"
    ports:
      - "8080:8080"
      - "8081:80"
    deploy:
      replicas: 3
    build:
      context: ../../
      dockerfile: ../Dockerfile-js
    environment:
      - PORT=80

#    restart: unless-stopped
    logging:
       driver: splunk
       options:
          splunk-url: "${SPLUNK_URL}"
          splunk-token: "${SPLUNK_TOKEN}"
          splunk-capath: "/mnt/splunk-ca-cert.pem"
          splunk-caname: "${SPLUNK_URL}"
          splunk-insecureskipverify: "false"
          tag: "{{.Name}}/{{.ID}}"
          labels: "NEurope"
          env: "${TARGET_NAME}"

When I'm running docker stack create -c filname.txt stack_name its searching for splunk-capath: "/mnt:/mnt/splunk-ca-cert.pem file in local system. I already copied this file in the container(when image built) same location but stack file is searching in the system instead of container. How can i make my stack file to look for the file inside the container???

Any help will be appreciated !!!

Thanks

Tags (1)
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 ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...