Michael Crosby c9379eb3fb 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>		2014-11-10 21:04:01 +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-10 21:04:01 +02:00
config_test.go	Removed runconfig.ParseSubcommand	2014-09-17 14:38:22 -07:00
exec.go	Address review comments.	2014-09-15 17:00:00 +00:00
hostconfig.go	Move security opts to HostConfig	2014-11-10 21:04:01 +02:00
merge.go	builder: some small fixups + fix a bug where empty entrypoints would not override inheritance.	2014-10-30 09:17:11 -04:00
parse.go	Move security opts to HostConfig	2014-11-10 21:04:01 +02:00
parse_test.go	Removed runconfig.ParseSubcommand	2014-09-17 14:38:22 -07:00