tests/docker: make "buildah bud" output similar to "docker build"
commita51d6a549361fd1a20dd2ac1d6a42ac0a4c708c7
authorCleber Rosa <crosa@redhat.com>
Thu, 12 Mar 2020 19:36:13 +0000 (12 15:36 -0400)
committerCleber Rosa <crosa@redhat.com>
Tue, 17 Mar 2020 23:16:16 +0000 (17 19:16 -0400)
tree3e149b2f39a616c667b4b9af5b439947017a22a7
parente631eb2e8b8c19d08c538eb29c01d53edbcc431b
tests/docker: make "buildah bud" output similar to "docker build"

Podman users will most often be using buildah to build containers.
Among the differences between "buildah bud|build-using-dockerfile" and
a traditional "docker build" is that buildah does not run a container
during build.

To the best of my knowledge and experiments, this means that runtime
variables, such as ENV from one base image will not propagate into
another.  The end result is that the location for the cross compiler
binaries, defined in the base "qemu/debian9-mxe" image, are not passed
through this image.  Consequently, the cross compilers are not on PATH
and the build fails.

Signed-off-by: Cleber Rosa <crosa@redhat.com>
Acked-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20200312193616.438922-3-crosa@redhat.com>
Signed-off-by: Cleber Rosa <crosa@redhat.com>
tests/docker/dockerfiles/debian-win32-cross.docker