From da92be30308725b9d19561251d74652eb9e4f02e Mon Sep 17 00:00:00 2001 From: Jose Diaz-Gonzalez Date: Fri, 6 Aug 2021 13:40:34 -0400 Subject: [PATCH] docs: clarify buildkit instructions There is no need for a reboot --- docs/deployment/builders/dockerfiles.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/deployment/builders/dockerfiles.md b/docs/deployment/builders/dockerfiles.md index f8aac829a..3bb77431a 100644 --- a/docs/deployment/builders/dockerfiles.md +++ b/docs/deployment/builders/dockerfiles.md @@ -145,7 +145,16 @@ RUN echo $NODE_ENV ### Building images with Docker Buildkit -If your Dockerfile is using Docker engine's [buildkit](https://docs.docker.com/develop/develop-images/build_enhancements/) (not to be confused with buildpacks), then the `DOCKER_BUILDKIT=1` environment variable needs to be set. One way to do this is to edit `/etc/environment` on your dokku host and reboot your instance. Note, for complete build log output, you should also set `BUILDKIT_PROGRESS=plain` in the same file. +If your Dockerfile is using Docker engine's [buildkit](https://docs.docker.com/develop/develop-images/build_enhancements/) (not to be confused with buildpacks), then the `DOCKER_BUILDKIT=1` environment variable needs to be set. Additionally, complete build log output can be forced via `BUILDKIT_PROGRESS=plain`. Both of these environment variables can be set as follows: + +```shell +# via config:set +dokku config:set --global DOCKER_BUILDKIT=1 BUILDKIT_PROGRESS=plain + +# on the /etc/default/dokku file +echo DOCKER_BUILDKIT=1 | sudo tee -a /etc/default/dokku +echo BUILDKIT_PROGRESS=plain | sudo tee -a /etc/default/dokku +``` #### Buildkit directory caching