Sample Installation below:
(This is for DB2 on ZLinux, change the db2_developer_c:11.1.4.4-s390x to your corresponding platform):
# docker login
# docker pull store/ibmcorp/db2_developer_c:11.1.4.4-s390x
# mkdir /data
# docker run -h db2server --name db2server --restart=always --detach --privileged=true -p 50000:50000 -p 55000:55000 --env-file .env_list -v /data:/database store/ibmcorp/db2_developer_c:11.1.4.4-s390x
# docker ps | grep db2
d3646927e758 store/ibmcorp/db2_developer_c:11.1.4.4-s390x "/var/db2_setup/lib/…" About a minute ago Up About a minute 0.0.0.0:50000->50000/tcp, 22/tcp, 60006-60007/tcp, 0.0.0.0:55000->55000/tcp db2server
# docker logs d3646927e758
(*) Creating users ...
(*) Creating instance ...
DB2 installation is being initialized.
Total number of tasks to be performed: 4
Total estimated time for all tasks to be performed: 309 second(s)
Task #1 start
Description: Setting default global profile registry variables
Estimated time 1 second(s)
Task #1 end
Task #2 start
Description: Initializing instance list
ls: cannot access /database/data/db2inst1/NODE0000: No such file or directory
Estimated time 5 second(s)
Task #2 end
Task #3 start
Description: Configuring DB2 instances
Estimated time 300 second(s)
Task #3 end
Task #4 start
Description: Updating global profile registry
Estimated time 3 second(s)
Task #4 end
The execution completed successfully.
For more information see the DB2 installation log at "/tmp/db2icrt.log.69".
DBI1446I The db2icrt command is running.
DBI1070I Program db2icrt completed successfully.
(*) Enabling TEXT_SEARCH for instance ...
DB2 installation is being initialized.
Total number of tasks to be performed: 4
Total estimated time for all tasks to be performed: 309 second(s)
Task #1 start
Description: Setting default global profile registry variables
Estimated time 1 second(s)
Task #1 end
Task #2 start
Description: Initializing instance list
Estimated time 5 second(s)
Task #2 end
Task #3 start
Description: Configuring DB2 instances
Estimated time 300 second(s)
Task #3 end
Task #4 start
Description: Updating global profile registry
Estimated time 3 second(s)
Task #4 end
The execution completed successfully.
For more information see the DB2 installation log at
"/tmp/db2iupdt.log.15631".
DBI1446I The db2iupdt command is running.
DBI1070I Program db2iupdt completed successfully.
06/04/2019 06:57:32 0 0 SQL1032N No start database manager command was issued.
SQL1032N No start database manager command was issued. SQLSTATE=57019
(*) Cataloging existing databases
(*) Applying Db2 license ...
LIC1402I License added successfully.
LIC1426I This product is now licensed for use as outlined in your License Agreement. USE OF THE PRODUCT CONSTITUTES ACCEPTANCE OF THE TERMS OF THE IBM LICENSE AGREEMENT, LOCATED IN THE FOLLOWING DIRECTOR
Y: "/opt/ibm/db2/V11.1/license/en_US.iso88591"
(*) Saving the checksum of the current nodelock file ...
(*) Updating DBM CFG parameters ...
DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed
successfully.
DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed
successfully.
DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed
successfully.
No Cgroup memory limit detected, instance memory will follow automatic tuning
DB2 State : Operable
DB2 has not been started
Starting DB2...
06/04/2019 06:57:47 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
(*) Starting TEXT SEARCH service ...
CIE00001 Operation completed successfully.
(*) User chose to create testdb database
(*) Creating database testdb ...
DB20000I The CREATE DATABASE command completed successfully.
DB20000I The ACTIVATE DATABASE command completed successfully.
06/04/2019 06:59:22 0 0 SQL1026N The database manager is already active.
SQL1026N The database manager is already active.
### Enabling LOGARCHMETH1
Database Connection Information
Database server = DB2/LINUXZ64 11.1.4.4
SQL authorization ID = DB2INST1
Local database alias = TESTDB
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
SQL1363W One or more of the parameters submitted for immediate modification
were not changed dynamically. For these configuration parameters, the database
must be shutdown and reactivated before the configuration parameter changes
become effective.
### Restarting DB2
06/04/2019 06:59:30 0 0 SQL1064N DB2STOP processing was successful.
SQL1064N DB2STOP processing was successful.
------------------------------
Carlos Mejia Johnson
------------------------------