We are excited to announce that we have updated our IBM MQ Docker container support statement. We have made two changes that are outlined in this blog post.
You can see the current support statement for IBM MQ in Docker containers on the Docker support on Linux systems Knowledge Center page

Changes to supported packages

Previously, only certain IBM MQ packages were supported in a Docker container environment. The supported packages list has now been expanded to include all packages currently available in MQ 9.0.3. With this change you are now able to use all features of IBM MQ in a container.

The list of packages currently supported is:

  • MQSeriesRuntime
  • MQSeriesServer
  • MQSeriesClient
  • MQSeriesSDK
  • MQSeriesSamples
  • MQSeriesJava
  • MQSeriesMan
  • MQSeriesJRE
  • MQSeriesGSKit
  • MQSeriesXRService
  • MQSeriesExplorer
  • MQSeriesFTAgent
  • MQSeriesFTBase
  • MQSeriesFTLogger
  • MQSeriesFTService
  • MQSeriesFTTools
  • MQSeriesAMS
  • MQSeriesAMQP
  • MQSeriesWeb
  • MQSeriesSFBridge

Changes to docker container shared namespaces

We have also updated our support statement regarding the use of docker containers shared namespaces. Previously if you wanted to connect local binding applications to a Queue Manager they had to run on the same container as the Queue Manager. Docker now includes support to share PID, IPC and UTS namespaces, this allows you to link two containers together to act as a single container.

With this new capability we have removed the restriction on local binding applications. There are requirements in order to properly utilize this new feature. These requirements are outlined in the Running local binding applications in separate containers Knowledge Center page.

By sharing two containers IPC, PID and UTS namespaces you can connect local bindings applications running in one container to a Queue Manager running in the other container. We see this as being particularly useful as it allows customers to connect local applications which interact with MQ via local bindings (for example MFT agents, IIB, WAS) to a Queue Manager without needing to include the application in the Queue Manager image.

Join The Discussion

Your email address will not be published.