Hello.
$ sudo docker version
Client: Docker Engine - Community
Version: 26.1.3
API version: 1.45
Go version: go1.21.10
Git commit: b72abbb
Built: Thu May 16 08:34:39 2024
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 26.1.3
API version: 1.45 (minimum version 1.24)
Go version: go1.21.10
Git commit: 8e96db1
Built: Thu May 16 08:33:34 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.32
GitCommit: 8b3b7ca2e5ce38e8f31a34f35b2b68ceb8470d89
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0
# Container start command
$ sudo docker run -h db2-12_1 --name db2-12_1 --restart=always --detach --privileged=true \
-p 25000:50000 -p 25001:50001 --env-file "${DIR?}/.env_list" -v "${DIR?}/database":/database icr.io/db2_community/db2
$ db2level
DB21085I This instance or install (instance name, where applicable:
"db2inst1") uses "64" bits and DB2 code release "SQL12012" with level
identifier "02030110".
Informational tokens are "DB2 v12.1.2.0", "s2505201240", "DYN2505201240AMD64",
and Fix Pack "0".
Product is installed at "/opt/ibm/db2/V12.1".
$ time db2 create db test
DB20000I The CREATE DATABASE command completed successfully.
real 74m58.681s
user 0m0.036s
sys 0m0.052s
75 min (!!!) for a simple `CREATE DATABASE` command. 15 min worse, than with 12.1.1.
Does anybody see the same behavior of containerized DB2 in docker?
------------------------------
Mark Barinstein
------------------------------