The Docker CLI (Command-Line Interface) docker build builds an image from a Dockerfile.
To list docker build options, type: docker build --help

Docker introduced new backend for builing images (buildkit) which doesn't expose intermediate containers.
To show intermediate containers, set the environment variable DOCKER_BUILDKIT before the docker build command: $ DOCKER_BUILDKIT=0 docker build [OPTIONS] PATH | URL | -

Usage: docker build [OPTIONS] PATH | URL | -

-t, --tag list Name and optionally a tag in the 'name:tag' format -f, --file string Name of the Dockerfile (Default is 'PATH/Dockerfile') -q, --quiet Suppress the build output and print image ID on success --no-cache Do not use cache when building the image --cache-from strings Images to consider as cache sources --pull Always attempt to pull a newer version of the image --build-arg list Set build-time variables --add-host list Add a custom host-to-IP mapping (host:ip) --rm Remove intermediate containers after a successful build (default true) --force-rm Always remove intermediate containers --cpu-period int Limit the CPU CFS (Completely Fair Scheduler) period --cpu-quota int Limit the CPU CFS (Completely Fair Scheduler) quota -c, --cpu-shares int CPU shares (relative weight) --cpuset-cpus string CPUs in which to allow execution (0-3, 0,1) --cpuset-mems string MEMs in which to allow execution (0-3, 0,1) -m, --memory bytes Memory limit --memory-swap bytes Swap limit equal to memory plus swap: '-1' to enable unlimited swap --cgroup-parent string Optional parent cgroup for the container --compress Compress the build context using gzip --disable-content-trust Skip image verification (default true) --iidfile string Write the image ID to the file --isolation string Container isolation technology --label list Set metadata for an image --network string Set the networking mode for the RUN instructions during build (default "default") -o, --output stringArray Output destination (format: type=local,dest=path) --platform string Set platform if server is multi-platform capable --progress string Set type of progress output (auto, plain, tty). Use plain to show container output (default "auto") --secret stringArray Secret file to expose to the build (only if BuildKit enabled): id=mysecret,src=/local/secret --security-opt strings Security options --shm-size bytes Size of /dev/shm --squash Squash newly built layers into a single new layer --ssh stringArray SSH agent socket or keys to expose to the build (only if BuildKit enabled) (format: default|<id>[=<socket>|<key>[,<key>]]) --stream Stream attaches to server to negotiate build context --target string Set the target build stage to build. --ulimit ulimit Ulimit options (default [])

You can use the option '--no-cache' to instruct Docker to not use cache when building the image:

Let's use this Dockerfile:
$ vi Dockerfile FROM ubuntu:20.04 RUN groupadd -r mtitek --gid=1001 && useradd -r -g mtitek --uid=1001 mtitek
The first time we build the Dockerfile we will get the following output:
$ docker build -t ubuntu-test-no-cache:20.04 . Sending build context to Docker daemon 2.048kB Step 1/2 : FROM ubuntu:20.04 20.04: Pulling from library/ubuntu 3ff22d22a855: Pull complete ... Digest: sha256:5d1d5407f353843ecf8b16524bc5565aa332e9e6a1297c73a92d3e754b8a636d Status: Downloaded newer image for ubuntu:20.04 ---> 1e4467b07108 Step 2/2 : RUN groupadd -r mtitek --gid=1001 && useradd -r -g mtitek --uid=1001 mtitek ---> Running in 9c61eb50e422 Removing intermediate container 9c61eb50e422 ---> 4fb16a88e392 Successfully built 4fb16a88e392 Successfully tagged ubuntu-test-no-cache:20.04
If we build again the Dockerfile we will get the following output:
$ docker build -t ubuntu-test-no-cache:20.04 . Sending build context to Docker daemon 2.048kB Step 1/2 : FROM ubuntu:20.04 ---> 1e4467b07108 Step 2/2 : RUN groupadd -r mtitek --gid=1001 && useradd -r -g mtitek --uid=1001 mtitek ---> Using cache ---> 4fb16a88e392 Successfully built 4fb16a88e392 Successfully tagged ubuntu-test-no-cache:20.04
You can notice that the step 2 has the mention '---> Using cache' which means that Docker just used the already built layer from this step.

Using local cache can speed up build time; especially when avoiding rebuilding image layers that take long time to build or take up large amounts of disk space.

In some cases (either to play safe or because we encountered some issues with the build) we might want to disable the cache, for that we use the option --no-cache:

$ docker build -t ubuntu-test-no-cache:20.04 --no-cache . Sending build context to Docker daemon 2.048kB Step 1/2 : FROM ubuntu:20.04 ---> 1e4467b07108 Step 2/2 : RUN groupadd -r mtitek --gid=1001 && useradd -r -g mtitek --uid=1001 mtitek ---> Running in 2db12b3ac7fa Removing intermediate container 2db12b3ac7fa ---> 776826ffa0fc Successfully built 776826ffa0fc Successfully tagged ubuntu-test-no-cache:20.04
You can notice that the step 2 has the mention '---> Running' which means that Docker is rebuilding again the image layer for that step.

By default Docker will use the Dockerfile in the current directory ('./Dockerfile'). You can use the option '-f FILE_NAME|FILE_LOCATION' to let Docker use a Dockerfile with a different name and/or a different path.

Let's create a Dockerfile named 'Dockerfile1':
$ vi Dockerfile1 FROM ubuntu:20.04
To use the Dockerfile 'Dockerfile1' (located in the current directory):
$ docker build -t ubuntu-custom-dockerfile1:20.04 -f Dockerfile1 .
You can also provide the full path where Dockerfile1 is located (e.g. '/opt/dockerfiles/'):
$ docker build -t ubuntu-custom-dockerfile1:20.04 -f /opt/dockerfiles/Dockerfile1 .

You can use the option '--build-arg' to set build arguments.

Let's use this Dokerfile:
$ vi Dockerfile ARG UBUNTU_TAG=20.04 FROM ubuntu:$UBUNTU_TAG ARG GROUP_ID=1001 ARG USER_ID=1001 RUN groupadd -r mtitek --gid=$GROUP_ID && useradd -r -g mtitek --uid=$USER_ID mtitek
Note that the arguments are used as variables in the Dockerfile using the syntax '$ARG_NAME'

If you don't specify a value for an argument in the build command, then the default values in the Dockerfile will be used:
$ docker build -t ubuntu-build-arg:20.04 . Sending build context to Docker daemon 2.048kB Step 1/5 : ARG UBUNTU_TAG=20.04 Step 2/5 : FROM ubuntu:$UBUNTU_TAG ---> 1e4467b07108 Step 3/5 : ARG GROUP_ID=1001 ---> Running in dbb369001ffb Removing intermediate container dbb369001ffb ---> ef9ee7e38909 Step 4/5 : ARG USER_ID=1001 ---> Running in b4d10e53c1b4 Removing intermediate container b4d10e53c1b4 ---> f39f6975eceb Step 5/5 : RUN groupadd -r mtitek --gid=$GROUP_ID && useradd -r -g mtitek --uid=$USER_ID mtitek ---> Running in 23379d190bc8 Removing intermediate container 23379d190bc8 ---> cdd722fb8929 Successfully built cdd722fb8929 Successfully tagged ubuntu-build-arg:20.04
To pass new values for the arguments, use the option '--build-arg':
$ docker build -t ubuntu-build-arg:18.04 \ --build-arg UBUNTU_TAG=18.04 \ --build-arg GROUP_ID=1002 \ --build-arg USER_ID=1003 \ . Sending build context to Docker daemon 2.048kB Step 1/5 : ARG UBUNTU_TAG=20.04 Step 2/5 : FROM ubuntu:$UBUNTU_TAG 18.04: Pulling from library/ubuntu 7595c8c21622: Pull complete ... Digest: sha256:a61728f6128fb4a7a20efaa7597607ed6e69973ee9b9123e3b4fd28b7bba100b Status: Downloaded newer image for ubuntu:18.04 ---> 2eb2d388e1a2 Step 3/5 : ARG GROUP_ID=1001 ---> Running in 24c2219ed67f Removing intermediate container 24c2219ed67f ---> 07271a6577d5 Step 4/5 : ARG USER_ID=1001 ---> Running in a69297eee3b7 Removing intermediate container a69297eee3b7 ---> dcdd02c80212 Step 5/5 : RUN groupadd -r mtitek --gid=$GROUP_ID && useradd -r -g mtitek --uid=$USER_ID mtitek ---> Running in d06c407a67e0 Removing intermediate container d06c407a67e0 ---> 37956d817713 Successfully built 37956d817713 Successfully tagged ubuntu-build-arg:18.04
Check that the arguments were used as expected:
$ docker run --rm -ti ubuntu-build-arg:18.04 /bin/bash -c 'cat /etc/passwd | grep mtitek' mtitek:x:1003:1002::/home/mtitek:/bin/sh