Public | Automated Build

Last pushed: a year ago
Short Description
1. Downloads from IBM and installs DB2 Express-C (10.5)
Full Description

Supported tags and respective Dockerfile links

What is DB2?

IBM DB2 is a family of database server products developed by IBM. These products all support the relational model, but in recent years some products have been extended to support object-relational features and non-relational structures, in particular XML.

Historically and unlike other database vendors, IBM produced a platform-specific DB2 product for each of its major operating systems. However, in the 1990s IBM changed track and produced a DB2 "common server" product, designed with a common code base to run on different platforms.

Set of images

This image is part of a set of images to create your DB2 environment:

This is the stack of images:

|   db2-sample   |  <-- Sample database (db2sampl)
|    db2inst1    |  <-- Default instance created (db2inst1:50000)
|  db2-instance  |  <-- Environment to create an instance
|   db2-install  |  <-- DB2 Express-C installed

How to use this image

This image will download and install DB2 LUW Express-C, but it will not create an instance nor a database.

NOTE: The GitHub repository has another Docker file that installs DB2 Enterprise Server Edition from the most recent fixpack; however, this installation requires a valid license after 90 days of usage. For this reason, this container is not published in the Hub.

In order to configure the DB2 environment, you can use the image angoca/db2-instance or you can create yourself the instance (db2icrt) and the database (db2 create db sample).

The installer is obtained direclty from IBM; however, this link is temporal. If the link is not longer valid, you just need to modify a page of the Wiki, by providing a new valid link. The instructions are in the same page, just visit:

For the DB2 installation, a provided response file is used. You can clone this repository and modify the response file for your own needs.

DB2 will be installed in the container in:

For Express-C:


For ESE:


Please, check the Travis-CI execution to see how this image is build.

Next steps

You will probably use the default instance db2inst1 listening on port 50000. You can use the angoca/db2-instance in order to prepare the environment for an instance with these characteristics.

If you want to configure the environment by yourself, you can run the container and execute the commands to create the instance (db2icrt), the database (db2 create db xxx), the security (useradd) and the other stuff.

Advantages of these images

The advantages to use this image instead of the other are:

  • The DB2 binary file is download semi-automatically. Just the wiki has to have the valid link. The other images requiere to modify the image with a valid link or to have DB2 installer/binaries locally in the machine.
  • This image has a mechanism to create more instances with a simple script that uses a response file. The instance owner can have any name; it is not limited to db2inst1 or something like db2instX where X is a number.
  • The environment can be configured in different ways. It is not limited to a fixed instance or database. The set of images provide different levels of flexible configuration.
  • The images are published in Docker in the angoca repository. The image is not created on the fly. The basic images are created from Dockerfiles, the other were published in the repository with the instance or database already created. As part of the publish, a corresponding documentation is provided.
  • The images can be found by performing a search in Docker. This allows to have a better visibility.
  • It was developed by a DB2 DBA. This makes this image appropriate not only for developers but also for DBAs and SysAdmins.
  • The complete installation and configuration is divided in different images. This makes the solution more flexible and easy to extent.
  • There is documentation. This is very important for new users to understand the structure of the

User Feedback


If you have any problems with or questions about this image, please contact us through a GitHub issue.

You can also reach the mainteiner via Twitter @angoca.


You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.

Docker Pull Command
Source Repository

Comments (0)