Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace Instana
Categories Sensor
Created by Guest
Created on Feb 16, 2023

Support different Container Runtimes in Helm Chart

Different container runtimes make their socket available under different paths inside their filesystem.

For example containerd socket is under: /var/run/containerd/containerd.sock

Dockers socket is under: /var/run/docker.sock

Currently only the docker socket is supported and hardcoded into the helm chart. It qould be great if that could be customized.

Idea priority Medium
  • Guest
    Feb 22, 2023

    We're running a eks 1.22 cluster with BottlerocketOS for worker nodes. Problem is that eks/bottlerocket uses docker as runtime which creates a dockershim-sock. The instana helm chart expects the containerd.sock. We have a workaround and are mounting the dockershim.sock to the path of containerd.sock, which works (See Support Request #29460). But we have to fork the helm chart and make some changes an it's always annoying to integrate our workaround.

    But because of removal of docker runtime in k8s 1.24 we can close this idea, because this will not be neccessary.

  • Admin
    Maria Elena Taglieri
    Feb 17, 2023

    Can you please share the details of the scenario you are trying to address?

    Which component are you exactly referring to?