llvm/docs/Docker.rst

13 We also provide an ``example`` image, which contains placeholders that one would need
14 to fill out in order to produce Dockerfiles for a new docker image.
34 A snapshot of a docker container filesystem is called a *docker image*.
35 One can start a container from a prebuilt docker image.
39 the docker image (see `official
41 details). A minimal Dockerfile typically contains a base image and a number
42 of RUN commands that have to be executed to build the image. When building a new
43 image, docker will first download your base image, mount its filesystem as
45 filesystem modifications, performed while building your image. When the build
46 process is finished, a diff between your image's final filesystem state and the
47 base image's filesystem is stored in the resulting image.
52 serve as a basis for anyone who wants to create their own Docker image with
54 upstream git repository when building the image.
56 The resulting image contains only the requested LLVM components and a few extra
57 packages to make the image minimally useful for C++ development, e.g. libstdc++
63 If you want to write your own docker image, start with an ``example/`` subfolder.
74 Here's a very simple example of getting a docker image with clang binary,
75 compiled by the system compiler in the debian8 image:
104 This will produce a new image ``clang-debian8:staging`` from the latest
106 After the image is built you can run bash inside a container based on your image
131 Which image should I choose?
134 differ in the base image that they use, i.e. they have a different set of
140 you should try debian8-based image.
143 you should choose nvidia-cuda-based image and use `nvidia-docker
147 image.
149 If you have a different use-case, you could create your own image based on
152 Any docker image can be built and run using only the docker binary, i.e. you can
161 debian8-based image using the latest ``google/stable`` sources for you:
173 Minimizing docker image size
176 the resulting image, even if they are removed in the following commands.
177 To minimize the resulting image size we use `multi-stage Docker builds
179 Internally Docker builds two images. The first image does all the work: installs
181 The first image is only used during build and does not have a descriptive name,
183 The second image is our resulting image. It contains only the built binaries