How to Use a Dockerfile to Build a Docker Image.
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
A Dockerfile is a text file of instructions which are used to automate installation and configuration of a Docker image. Dockerfiles make it easy to deploy multiple Docker containers without having to maintain the same image across multiple virtual machines. Instructions are executed in the order they appear in the Dockerfile, which makes using and updating them clear and intuitive. This article covers the basics, with an example, of how a Dockerfile works.
Familiarize yourself with our Getting Started guide, create and update a Linode, and install Docker. Alternatively, you can quickly deploy an updated, Docker-enabled Linode with the Docker Marketplace App.
Ensure your Linode is secure by following our guide on Setting Up and Securing a Compute Instance.
This guide assumes you are comfortable with using the Docker command-line interface (CLI). To learn more about the Docker CLI, check out their documentation.
A Dockerfile is a script that carries out different commands and actions to build a Docker image, which can then be used to deploy a Docker container. The commands and information within the Dockerfile can be configured to use specific software versions and dependencies for stable deployments. You can also use a Docker registry to store and access your public (or private) Docker images.
Once a Dockerfile is written, you can use the
docker build command to generate a Docker image based on the Dockerfile’s instructions. Then, you can deploy a container based on the image with commands like
docker run or
Here are common instructions that you can use in your Dockerfiles to build images:
- FROM: Define the base image, such as
debian, used to start the build process. Required for each Dockerfile.
- MAINTAINER: Define the full name and email address of the image creator.
- ENV: Set environment variables that persist when the container is deployed.
- ARG: Set a passable build-time variable. Can be used as an alternative to
ENVto create a variable that does not persist when the container is deployed from the image.
- RUN: Execute commands, such as package installation commands, on a new image layer.
- CMD: Execute a specific command within the container that is deployed with the image, or set default parameters for an
ENTRYPOINTinstruction. Only one is used per Dockerfile.
- ENTRYPOINT: Set a default application to be used every time a container is deployed with the image. Only one is used per Dockerfile.
- USER: Set the UID (the username) to run commands in the container.
- WORKDIR: Set the container path where subsequent Dockerfile commands are executed.
ENTRYPOINTcan each be run in shell form, which takes normal arguments, or exec form, which takes arguments as a JSON array. Because exec form does not invoke a command shell, it is generally preferred and utilized in this guide.
- ADD: Copy files from a source to the image’s filesystem at the set destination with automatic tarball and remote URL handling.
- COPY: Similar to
ADDbut without automatic tarball and remote URL handling.
- VOLUME: Enable access from a specified mount point in the container to a directory on the host machine.
- EXPOSE: Expose a specific port to enable networking between the container and the outside world.
Next, we will create an example Dockerfile that utilizes some of these commands.
To create the Dockerfile:
At the command prompt (either via SSH or Lish in the Linode Manager), create and change to a new directory:
mkdir ~/mydockerbuild && cd ~/mydockerbuildThis places the Docker build directory in your home directory. As a matter of good practice, do not store the Dockerfile in your home directory itself or the server’s root directory. Instead, create a separate directory and place all necessary files within it (alongside the Dockerfile) as shown in this guide.
Create an example Dockerfile:
Open the Dockerfile using the text editor of your choice (for this example, we use nano):
Copy the following example into your Dockerfile. This creates a Dockerfile that generates a Debian image, sets the maintainer information, and simply returns “Hello, Sunshine!” when run:
- File: example_dockerfile
1 2 3
FROM debian MAINTAINER Jane Doe firstname.lastname@example.org CMD ["echo", "Hello, Sunshine!"]
Save the Dockerfile.
cat example_dockerfileand ensure the text from above is included.
Build the image from the Dockerfile using the
docker build command:
docker build ~/mydockerbuild -f example_dockerfile -t example_image
Labelling your image with
example_image makes it easier to deploy a container in the next step.
The output should look something like this:
Sending build context to Docker daemon 4.096kB Step 1/3 : FROM debian ---> 4a7a1f401734 Step 2/3 : MAINTAINER Jane Doe email@example.com ---> Running in fdd81bd8b5c6 Removing intermediate container fdd81bd8b5c6 ---> 1253842068a3 Step 3/3 : CMD ["echo", "Hello, Sunshine!"] ---> Running in d33e1bacf1af Removing intermediate container d33e1bacf1af ---> a5d95e138b97 Successfully built a5d95e138b97 Successfully tagged example_image:latest
As you can see, the instructions from
example_dockerfile are executed in order. The image labelled
example_image is now ready for running to deploy a container.
Running the image you just built to deploy a Docker container is now as easy as entering the following:
docker run example_image
A new container based on
example_image is deployed, and the command specified in the
CMD instruction is then executed from the container with the following output:
docker runcommand is executed and the Docker image is not available in your current working directory, it is pulled from the Docker registry instead.
Congratulations! You’ve built your first Dockerfile and run your first Docker image.
For more examples and information on using Dockerfiles with Docker images and containers, see:
Docker’s Dockerfile Best Practices.
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on