Try setting DOCKER_BUILDKIT=1 as an environment variable, then run `docker build ...` however you'd normally do. I found a basic overview of what buildkit does in this blog post: https://www.cloudsavvyit.com/12441/what-is-dockers-buildkit-and-why-does-it-matter/
On Tue, Apr 26, 2022 at 11:22 AM sebb <seb...@gmail.com> wrote: > > On Tue, 26 Apr 2022 at 16:51, Matt Sicker <boa...@gmail.com> wrote: > > > > One thing to consider for optimizing the Docker build here is the > > buildkit feature: > > https://docs.docker.com/engine/reference/commandline/buildx/ and > > https://docs.docker.com/engine/reference/commandline/builder/ > > Thanks, but I cannot work out how one might use that. > > > There is also buildpacks.io which is related, though I'm not sure if > > it's a feature built into Docker or with other tools only. > > > > On Tue, Apr 26, 2022 at 10:11 AM sebb <seb...@gmail.com> wrote: > > > > > > The Docker build currently targets Ubuntu 20.04, which I think is > > > known as Focal Fossa. > > > > > > However there is a reference in the build to bionic, which is a > > > previous release: > > > > > > echo "deb http://opensource.wandisco.com/ubuntu bionic svn110" > > > > > > Does that still make sense? > > > > > > Also I find that there seem to be frequent rebuilds, which can take > > > quite a long time to complete. > > > There must be some some items in the long RUN command that are being > > > updated. > > > Any idea how to find out which they are? > > > > > > AIUI the reason for grouping lots of updates together is to reduce the > > > number of intermediate caches that are generated, but the disadvantage > > > is that a single update forces the entire command to be rebuilt. > > > Ideally frequently changing software should be installed separately > > > after the stable stuff. But how to find this out? > > > > > > Does it make sense to start on the next version of Ubuntu? > > > > > > Sebb
