-
-
Notifications
You must be signed in to change notification settings - Fork 794
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
Changing log options doesn't restart container #985
Comments
Confirmed issue to still be present, exactly as described above, as of July 2018 docker cookbook version: 4.4.0 |
Somebody is going to solve it? this is an issue from 2018... |
Any updates? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cookbook version
4.1.1
Chef-client version
Chef 12.18.31
Platform Details
Ubuntu 16.04
Scenario:
If you change the 'logging' options it does not reconfigure / restart the container
Steps to Reproduce:
Then change the log_driver or log_opts
Then run chef.
Then run a docker inspect, you will find the 'splunk' logger isn't there
Workaround
Deleting and recreating the container by hand fixes the issue
Looking at docker inspect shows the splunk options now
Expected Result:
Chef should restart the container just like it does if you change any other options (e,g, volumes, labels, tags)
Actual Result:
Chef does not restart or reconfigure the container on any logging changes
The text was updated successfully, but these errors were encountered: