From e556e6643e5d2300a38e4373bde45e83178becaf Mon Sep 17 00:00:00 2001 From: Rob Austein Date: Mon, 11 Feb 2019 07:39:38 +0000 Subject: debootstrap, XiLinx installation. --- stage1/Dockerfile | 17 ++++++----------- 1 file changed, 6 insertions(+), 11 deletions(-) (limited to 'stage1/Dockerfile') diff --git a/stage1/Dockerfile b/stage1/Dockerfile index 2881772..db6fad3 100644 --- a/stage1/Dockerfile +++ b/stage1/Dockerfile @@ -1,17 +1,12 @@ -FROM debian:jessie +FROM xilinx:debootstrap +# Finish debootstrap (stage0 did debootstrap --foreign) + +RUN sed -i '/mount -t proc /d; /mount -t sysfs /d' /debootstrap/functions && \ + /debootstrap/debootstrap --second-stage + # Our goal here is just to load the XiLinx tarball into a Debian Jessie image. # Overriding reason for making this a separate image: we don't want to have # to send 6GB of build context every time we touch a later stage. ADD Xilinx_ISE_DS_Lin_14.7_1015_1.tar /xilinx-unpack/ - -# Given our general paranoia level we probably should be building our -# own debian:jessie image from debootstrap, but leave that for another -# day. Process is reasonably well documented: instead of starting -# from a base image, start by running debootstrap in --foreign mode, -# import that into an initial Docker image, then run `debootstrap -# --second-stage` in the next Dockerfile. Something like: -# -# sudo debootstrap --foreign jessie jessie_chroot -# sudo tar -C jessie_chroot -c . | docker import - my-debian:jessie -- cgit v1.2.3