Amy Fong 960aff31ba docker engine not running ... In yocto builds, preprocessing of binaries can happen after the install phase. Some of these can modify the size/sha1sum of the binaries. e.g. A new .gnu_debuglink can happen docker will not start because of these modifications. Docker initially does a sha1sum of dockerinit to identify the dockerinit that it was built with, this is done for security and for compatibility reasons. Since this checking is disabled, we should rely on rpm tests for validation of the binary instead. Signed-off-by: Amy Fong <amy.fong@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>		2015-04-11 00:22:37 -04:00
..
cgroup-lite	Add cgroup-lite	2015-03-17 09:46:32 -04:00
criu	criu: upgrade from version from 1.2 to 1.4	2015-03-30 23:45:22 -04:00
docker	docker engine not running	2015-04-11 00:22:37 -04:00
docker-registry	docker-registry: relax python-requests version specification	2015-03-30 23:43:27 -04:00
lxc	lxc: fix building when B != S	2015-04-11 00:20:49 -04:00