Dependency on systemd added in DB2 11.1.1.1 prevents installation in RHEL 7.3 docker container

Idea created for the RFE closed wrongly - http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=103478

21 vote(s) as of Mar 13, 2019

We use Docker containers to perform automated testing of our products on various prerequisite software packages including DB2 and have scripted the installation of these packages on the stock RHEL image currently registry.access.redhat.com/rhel7.3:latest. We have discovered that our automated installation script for DB2 which works for Version 10.1.x, 10.5.x & 11.1 does not work with the latest DB2 version 11.1.1.1 as db2setup returns an exit code of 1 because of a failure to start the DB2 Fault Monitor. As these images are auto-provisioned, the non-zero exit code due to the warning about the failure to load DB2 Fault Monitor during installation kills the auto-provisioning process. An Investigation carried out with help from DB2 support via a PMR revealed that the cause of the issue as a new dependency on systemd added in Version 11.1.1.1 without any provision to revert to the behaviour of previous releases. As you are probably aware, the Hypervisors tab on: http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=3AF321105FF411E6865BC3F213DB63F7&osPlatforms=Linux&duComponentIds=S010|S004|S015|S008|S009|S011|S005|S013|S003|A001|A006|A014|A007|A002|A016|A012&mandatoryCapIds=183|25&optionalCapIds=30|341|47|17|1|131|20|28#! claims DB2 11.1.1.1 supports Docker versions greater than 1.8 with no guest operating system restrictions - We're currently using Docker version 1.12 with the stock RHEL 7.3 image 'registry.access.redhat.com/rhel7.3:latest' which I believe should be a supported environment but the DB2 11.1.1.1 installation doesn't complete successfully in it.

Use case:We've implemented an automated test infrastructure which runs hundreds of test cases against a matrix of different versions of prerequisite software. The inability to automatically install the latest version of DB2 in what should be a supported environment is a serious impediment.