I'm getting SQL1042C An unexpected system error occurred when running the build script.

If I add the following to the Dockerfile things work for me.

Setup instance directory as an ext4 volume, db2 cannot write to AUFS

VOLUME /home/db2inst1

Are others not seeing this issue?
Also see that you removed the 'sysctl -w kernel.shmmax=18446744073709551615' command from the startup script. Have you started to simply set this on the docker host ?

Hi,

I found that you wrote the first image to run DB2. It is very interesting. I am a DB2 DBA, and based on yours and other images, I create my own set of images.

If you want to take a look:

• https://github.com/angoca/db2-docker
• https://hub.docker.com/u/angoca/

I would like to invite the people that already create a DB2 docker image towork together for a better solution. I am member of a GitHub organizacion called db2-coders, and I propose you to be part of it, and let's community image.

Seems like DB2 is running out of memory, even while running in privileged mode and with shmmax set.

IBM sez:

At a minimum, a DB2 database system requires 256 MB of RAM. For a system running just a DB2 product and the DB2 GUI tools, a minimum of 512 MB of RAM is required. However, 1 GB of RAM is recommended for improved performance. These requirements do not include any additional memory requirements for other software that is running on your system.
When determining memory requirements, be aware of the following:
DB2 products that run on HP-UX Version 11i for Itanium-based systems require 512 MB of RAM at a minimum.

For IBM® data server client support, these memory requirements are for a base of five concurrent client connections. You will need an additional 16 MB of RAM per five client connections.
Memory requirements are affected by the size and complexity of your database system, and the extent of database activity and the number of clients accessing your system.

For DB2 server products, the self-tuning memory feature simplifies the task of memory configuration by automatically setting values for several memory configuration parameters. When enabled, the memory tuner dynamically distributes available memory resources among several memory consumers including sort, the package cache, the lock list and buffer pools.
DB2 requires paging, also called swap to be enabled. This configuration is required to support various functions in DB2 which monitor or depend on knowledge of swap/paging space utilization. The actual amount of swap/paging space required varies across systems and is not solely based on memory utilization by application software. It is only strictly required by DB2 on the Solaris and HP platforms due to their use of early paging space allocation.

A reasonable minimum swap/paging space configuration for most systems is 25-50% of RAM. Solaris and HP systems with many small databases or multiple databases tuned by STMM might require a paging space configuration of 1 x RAM or higher. These higher requirements are due to virtual memory pre-allocated per database / instance, and retained virtual memory in the case of STMM tuning multiple databases. Additional swap/paging space might be wanted to provision for unanticipated memory overcommitment on a system.

Hi Jeff,
I keep getting this error during the build:
[..]
Task #38 start
Description: Updating global profile registry
Estimated time 3 second(s)
Task #38 end

A minor error occurred while installing "DB2 Express-C " on this computer.
Some features may not function correctly.

For more information see the DB2 installation log at
"/tmp/db2_install.log.7".
2015/01/28 18:18:11 The command [/bin/sh -c /cache/expc/db2_install -b /opt/ibm/db2/V10.5] returned a non-zero code: 1

Any clue of what could I've been doing wrong/missing or how can I get more details about this error?

Docker version 1.1.2, build d84a070/1.1.2

Thanks!

Hi Jeff,

I recently created my own DB2 container and had to overcome many of these issues myself, before discovering you're Dockerfile. we were literally working on this at roughly the same time.

I have one issue which I cannot seem to get around. For whatever reason, the db2 create statement takes extremely long in certain situations.

Here are some examples of timing that statement on various configurations.

1. On a VirtualBox VM on a host with SSD using devicemapper backend = 15seconds
2. On a CoreOS host with SATA disk using btrfs = 30 minutes
3. On a CoreOS host with SARA using devicemapper = 40 minutes
4. On a CoreOS host with SSD using btrfs = 15 minutes
5. On a CoreOS host with SSD using devicemapper/ext4 = 20 minutes
6. On a CentOS host with SSD using a loopback device and a sparse file = 5 seconds
7. On a VirtualBox VM on a host with SSD using btrfs = 30 seconds

I can't seem to figure this one out. All I can say is that I've been used to this statement taking around 10-30seconds but was shocked to find it take 40minutes on production hardware where my build server is located. Do you have any idea what could be causing this? The extremes are very extreme...5 seconds on the one hand and 40 minutes on the other...

Because it's least likely to change (and takes a really long time to complete), it makes sense to add the tar.gz install file first thing, so we never 😉 have to rebuild that image.

I'm unable to create a folder in the /var/custom folder in the base image store/ibmcorp/db2_developer_c:11.1.4.4-x86_64

This is the error I get when I try to build the image
Step 2/4 : RUN mkdir /var/custom/DViewWE
---> Running in aaf9b4845192
mkdir: cannot create directory '/var/custom/DViewWE': No such file or directory

Here is the dockerFile
FROM store/ibmcorp/db2_developer_c:11.1.4.4-x86_64

RUN mkdir /var/custom/DViewWE

COPY CreateDViewWEDB.sql /var/custom
RUN chmod a+x /var/custom/CreateDViewWEDB.sql

Need help.

Hello

I have done some experiments around db2 on docker and was able to start db2 in a docker container without --privilege=true but using limited privileges
I have have published my finding in a blog here
http://db2indocker.blogspot.in/
Please check it out and let me know your comments

Create an image and upload it to the docker registry, something like:

db2start
db2 create database sample
db2stop

Commit it, and bingo bango bongo.