It is good practice to use an explicit registry for referencing the base image. This is because some distros will inject their own registries into the search path. For example registry.fedoraproject.org comes ahead of docker.io. Using an explicit registry avoids wasting time querying multiple registries for images that they won't have. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Reviewed-by: Wainer dos Santos Moschetta <wainersm@redhat.com> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com> Reviewed-by: Alex Bennée <alex.bennee@linaro.org> Message-Id: <20210623142245.307776-5-berrange@redhat.com> Message-Id: <20210709143005.1554-13-alex.bennee@linaro.org>
19 lines
636 B
Docker
19 lines
636 B
Docker
#
|
|
# Docker multiarch cross-compiler target
|
|
#
|
|
# This docker target uses the current development version of Debian as
|
|
# a base for cross compilers for building test binaries. We won't
|
|
# attempt to build QEMU on it yet given it is still in development.
|
|
#
|
|
# On its own you can't build much but the docker-foo-cross targets
|
|
# build on top of the base debian image.
|
|
#
|
|
FROM docker.io/library/debian:bullseye-slim
|
|
|
|
# Duplicate deb line as deb-src
|
|
RUN cat /etc/apt/sources.list | sed "s/^deb\ /deb-src /" >> /etc/apt/sources.list
|
|
|
|
# Install common build utilities
|
|
RUN apt update && \
|
|
DEBIAN_FRONTEND=noninteractive apt install -yy eatmydata
|