From 960aff31ba2b02972b93f0a0ec45a2fba2987f48 Mon Sep 17 00:00:00 2001 From: Amy Fong Date: Thu, 9 Apr 2015 14:19:48 -0400 Subject: 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 Signed-off-by: Bruce Ashfield --- recipes-containers/docker/docker_git.bb | 1 + 1 file changed, 1 insertion(+) (limited to 'recipes-containers/docker/docker_git.bb') diff --git a/recipes-containers/docker/docker_git.bb b/recipes-containers/docker/docker_git.bb index a683840d..cb546161 100644 --- a/recipes-containers/docker/docker_git.bb +++ b/recipes-containers/docker/docker_git.bb @@ -24,6 +24,7 @@ SRC_URI = "\ file://docker.service \ file://docker.init \ file://hi.Dockerfile \ + file://disable_sha1sum_startup.patch \ " # The golang-cross embeds a compiler invocation for the pre-parser -- cgit v1.2.3-54-g00ecf