IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Delivered
Workspace Db2
Created by Guest
Created on Mar 14, 2019

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

Idea created for the RFE closed wrongly -

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 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 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 without any provision to revert to the behaviour of previous releases. As you are probably aware, the Hypervisors tab on:|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 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 '' which I believe should be a supported environment but the DB2 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.

  • Guest
    Mar 5, 2020

    When it says shipped does this mean it has been fixed? If so how?