Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
298 lines (190 sloc) 9.48 KB

|CyVerse logo|_

|Home_Icon|_ Learning Center Home

Building a container from a Dockerfile

One of the most important aspects of Docker is that everything in the container can be neatly documented in a Dockerfile - a plain text document specifying the steps used to build the container. Let's build a container that will run fastqc a popular bioinformatics tool for checking the quality of DNA sequencing reads.

First, we will try to install fastqc on the ubuntu image just as if we were installing it on an ordinary ubuntu machine:

  1. Open a bash session on an ubuntu container
docker run -it ubuntu bash
  1. Next we will download and unzip the fastqc program

Unfortunately we get the following error

bash: wget: command not found

This is because the containerized version of Ubuntu really is a minimal set of tools. Many small tools you expect to be on the container will need to be installed.

  1. Let's install wget, unzip, and a few other dependancies
# update the package list
apt-get update

# install the needed packages including java and a perl library which we
# need for fastqc
apt-get install wget unzip default-jdk libfindbin-libs-perl
  1. Now let's attempt to install fastqc
  1. Let's configure fastqc and then test on some sample data
# make fastqc executable
chmod 755 /FastQC/fastqc

# add fastqc to the system path by linking to /bin
ln -s /FastQC/fastqc /bin

# get some sample data

#run FastQC
fastqc small.fastq

Now that we know fastqc works, we can record the steps we went through in a Dockerfile. Currently, when we exit the container we have been working interactively in (in the bash shell) all of our work will be lost. Creating a Dockefile will allow us to build a new container image with all of our configuration saved.


A Dockerfile is a textfile and has a simple format

# Comment

  INSTRUCTION arguments

Comments start with a "#" and instructions start with one of a few basic commands. Some of the most important are:

  • FROM: Describes an existing Docker image to start building from. You can start from 'scratch', but will usually start from a basic image like the Ubuntu machine we have used above.
  • RUN: Runs a command as you would at the shell. This creates a Docker layer in the image (See Dockerfile instructions for more on this).
  • LABLE: Allows you to add metadata to your image in a "key=value" format.
  • EXPOSE: Indicates specific ports to be listened to.
  • ENV: Allows you to set environment variables.
  • ADD: Allows you to copy files into the container when it is built
  • COPY: Allows you to copy files into the contain when it is built (See Dockerfile for the subtle differences between ADD and COPY behavior).
  • ENTRYPOINT: Specifies a specific application to run when the container is run. See also Dockerfile for the differences between this and a similar instruction "CMD".

We can create a Dockerile using the nano text editor. Notice the comments in the text, there are some specific ways you will want to run commands in the Dockerfile

6. Open a text editor (outside of the container) and create a Dockerfile. We will do this in an empty directory.

mkdir dockerfile
cd dockerfile
nano Dockerfile
  1. Copy or write the following
# Build this container from the official Ubuntu Image
# Make sure to use a tag that specifies version
# i.e. ubuntu:bionic-20181112 not just ubuntu
# The first line of your Dockerfile must be a FROM instruction
FROM ubuntu:bionic-20181112

# Add some metadata to describe our container
LABEL maintainer="yourname"
LABEL maintainer_email="youremail"
LABEL version="1.0"

# The ADD command will fetch and unzip the fastqc software

# We will run some commands just as we did in bash
# Notice that we use the -y option for our apt-get since we can't say y during the build process
# We also want to run the apt-get update in the same line as our install
# We connect those commands with && to specify that the first command must exit
# successfully before the second command is executed
# We won't install wget since the ADD command eliminates the need

RUN apt-get update -y && apt-get install -y\

# We will modify the permission on the software and create our symbolic link

RUN unzip / && chmod 755 /FastQC/fastqc && ln -s /FastQC/fastqc /bin

# We will define fastqc as the application to run when this container starts
ENTRYPOINT ["fastqc"]
  1. Next, we will build our container with the following command
# -t specifies a name and version tag for the image
# . specifies the "build context", the path to any needed files for the build
# should exist. In our case the Dockerfile is the only file needed

docker build -t fastqc:1.0 .

9. After the build is completed we should see our container in the list of Docker images on our machine

docker images

REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
fastqc              1.0                 0ab4e3a50edc        3 minutes ago       774MB

10. Finally, we can use our fastqc machine on data. Download the data on your host machine, and then use the created Docker image as if it were an application

mkdir ~/data
cd ~/data

# we use the -v flag to mount our ~/data directory (outside container)
# to /data (inside the container; it will be created when this command is run)
# We then specify the file for the fastqc program to run on.

docker run -v ~/data:/data fastqc:1.0 /data/small.fastq

You should now have two outputs in your ~/data directory small_fastqc.html and


A Dockerfile allows you to transparently document all the dependancies and steps needed to describe a software tool. You can then run this tool as a Docker container for full reproducibility.

Next Steps:

Additional information, help

Search for an answer: |CyVerse Learning Center| or |CyVerse Wiki|

Post your question to the user forum: |Ask CyVerse|

Fix or improve this documentation

|Home_Icon|_ Learning Center Home

You can’t perform that action at this time.