We’re running Drone on docker on VM’s and trying to configure an alternate log-driver - in this case splunk - but the spawned pipeline containers still use the json-file driver.
I’m not sure if this is supported, but we configured the docker daemon config to use the splunk log-driver as follows:
This works for the droner-runner-docker container - which uses the splunk log-driver - and we can see the runner logs in splunk, but not our pipeline containers - which still use json-file driver. I’m guessing that json-file is getting overriden by drone when it creates pipeline containers. Presumably, this is so that drone can parse the output for the UI - but that’s just a guess.
It didn’t appear that using DRONE_DOCKER_CONFIG to mount and pass this configuration was an option either.
Is this correct? Is there an alternate configuration method here that I missed?