Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting docker_container's log_driver property to splunk doesn't have any effect #836

Open
talcloudshare opened this issue Mar 28, 2017 · 1 comment

Comments

@talcloudshare
Copy link

talcloudshare commented Mar 28, 2017

Cookbook version

2.15.2

Chef-client version

12.17.44

Platform Details

Linux ubuntu-16 4.4.0-66-generic

Scenario:

I'm trying to set a container's logging driver to be Splunk, but it doesn't seem to have any effect - logging driver remains json-file

More information on Splunk logging driver - https://docs.docker.com/engine/admin/logging/splunk

Steps to Reproduce:

docker_container ... do
  ...
  log_driver 'splunk'
  log_opts [
    "splunk-token=#{splunk_token}",
    "splunk-url=#{splunk_host}",
    "splunk-insecureskipverify=true",
    "splunk-source=...",
    "splunk-sourcetype=..."
  ]
  ...
end

Expected Result:

root@ubuntu-16:~# docker inspect -f '{{.HostConfig.LogConfig.Type}}' CONTAINER_ID
splunk

Actual Result:

root@ubuntu-16:~# docker inspect -f '{{.HostConfig.LogConfig.Type}}' CONTAINER_ID
json-file
@iennae
Copy link
Contributor

iennae commented Mar 31, 2017

This does look like a bug, but we do need to do more investigation. Thanks for reporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants