Skip to Main Content
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 Not under consideration
Workspace Spectrum LSF
Created by Guest
Created on Feb 12, 2019

Enable override of -u flag to docker in LSF

The docker LSF integration would be more useful if the user inside the container was not forced to be LSB_SUB_USER. It's not clear where this -u flag is being added to the docker command by LSF. The construction of this flag does not appear to be happening in the provided python scripts. This should be admin-configurable only, so that security precautions can be taken before, for example, allowing the user to be root in the container (likely the most common way to use docker containers), or to prevent the user from running as another client.

  • Guest
    Mar 19, 2019

    The general requirement is that users do not gain any privileges and that all jobs run as the user who submitted them. This is consistent across docker, singularity, shifter etc.
    The key point of the integration is that users are not part of the docker user group, and do not gain privileges and cannot impersonate another user.

    If the container is assuming that the user has privileges to do impersonation, especially root, then the submitting user also needs to be in the docker user group, and the container should just be executed directly not using the integration.