From 71861b6ea54738950ac5c8e83e78bbd1215a11ed Mon Sep 17 00:00:00 2001 From: Rob Austein Date: Sun, 10 Feb 2019 23:58:32 +0000 Subject: Separate into multiple stages, at least during development. Docker is pretty clever about not rebuilding stuff, but simply having the 6GB XiLinx tarball in the build context is painful, so let's avoid that as much as we can. --- stage1/Dockerfile | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 stage1/Dockerfile (limited to 'stage1') diff --git a/stage1/Dockerfile b/stage1/Dockerfile new file mode 100644 index 0000000..2881772 --- /dev/null +++ b/stage1/Dockerfile @@ -0,0 +1,17 @@ +FROM debian:jessie + +# 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