Michael Crosby 294843ef23 Move security opts to HostConfig ... These settings need to be in the HostConfig so that they are not committed to an image and cannot introduce a security issue. We can safely move this field from the Config to the HostConfig without any regressions because these settings are consumed at container created and used to populate fields on the Container struct. Because of this, existing settings will be honored for containers already created on a daemon with custom security settings and prevent values being consumed via an Image. Signed-off-by: Michael Crosby <crosbymichael@gmail.com> Conflicts: daemon/create.go changing config to hostConfig was required to fix the build		2014-11-25 01:02:30 +02:00
..
compare.go	Move volumesfrom to hostconfig	2014-04-08 21:45:06 +00:00
config.go	Move security opts to HostConfig	2014-11-25 01:02:30 +02:00
config_test.go	Remove unused sysinfo parameter to runconfig.Parse	2014-11-14 18:20:54 -08:00
exec.go	Cleanup exec API docs and available params	2014-11-21 21:11:07 -05:00
hostconfig.go	Move security opts to HostConfig	2014-11-25 01:02:30 +02:00
merge.go	Merge pull request #8770 from LK4D4/logrus_support	2014-10-27 09:05:24 -07:00
parse.go	Move security opts to HostConfig	2014-11-25 01:02:30 +02:00
parse_test.go	Remove unused sysinfo parameter to runconfig.Parse	2014-11-14 18:20:54 -08:00