From cfd0a6ff1fd9db9ab359a423d4529b76184c7b98 Mon Sep 17 00:00:00 2001 From: Adrien Ferrand Date: Mon, 26 Oct 2020 23:20:27 +0100 Subject: [PATCH] Remove usage of buildkit (#8408) Fixes #8355 During the troubleshooting of #8355, I came to the conclusion that using buildkit was creating the problem. Without it all docker images are built correctly. Initially buildkit was enabled to avoid a building problem in Azure Pipeline, but I also found in my recent tests that this problem was not there anymore. You can find more details about the troubleshooting and reasoning in #8355. As a consequence, I disable the usage of buildkit in this PR which will solve the issue. --- tools/docker/build.sh | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/tools/docker/build.sh b/tools/docker/build.sh index 9fcc4473c..e3ff5707a 100755 --- a/tools/docker/build.sh +++ b/tools/docker/build.sh @@ -12,19 +12,6 @@ IFS=$'\n\t' # given value is only the base of the tag because the things like the CPU # architecture are also added to the full tag. -# As of writing this, runs of this script consistently fail in Azure -# Pipelines, but they are fixed by using Docker BuildKit. A log of the failures -# that were occurring can be seen at -# https://gist.github.com/2227a05622299ce17bff9b0da714a1ff. Since using -# BuildKit is supposed to offer benefits anyway (see -# https://docs.docker.com/develop/develop-images/build_enhancements/ for more -# information), let's use it. -# -# This variable is set inside the script itself rather than in something like -# the CI config to have a consistent experience when this script is run -# locally. -export DOCKER_BUILDKIT=1 - WORK_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null && pwd )" REPO_ROOT="$(dirname "$(dirname "${WORK_DIR}")")" source "$WORK_DIR/lib/common"