Updates Chef Server to v12.19.31 and various other cleanups#3
Open
jeroenj wants to merge 17 commits intosunggun-yu:masterfrom
Open
Updates Chef Server to v12.19.31 and various other cleanups#3jeroenj wants to merge 17 commits intosunggun-yu:masterfrom
jeroenj wants to merge 17 commits intosunggun-yu:masterfrom
Conversation
As of v12.16.1 postgres 9.6 is used which no longer uses that value: https://github.com/chef/chef-server/blob/master/RELEASE_NOTES.md#12161-2017-08-15
This also means that it no longer needs to run in privileged mode. 🎉 * chef/chef-server#1337 * chef/chef-server#1328
rsync is required to be able to take backups: https://docs.chef.io/server_backup_restore.html#backup
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
sysctlcalls fromentrypoint.shwhich results the container being able to run unprivileged.When running this image unprivileged the following warnings are shown when the container starts:
However everything works as expected. If desired
--privilegedcan still be used to avoid those.I'm currently running these changes in production.