ibmcom/mq
Versions of IBM MQ after 9.2.4 are no longer hosted on Docker Hub. Instead, you can download the latest version from the IBM Container Registry.
IBM® MQ is messaging middleware that simplifies and accelerates the integration of diverse applications and business data across multiple platforms. It uses message queues to facilitate the exchanges of information and offers a single messaging solution for cloud, mobile, Internet of Things (IoT) and on-premises environments.
By connecting virtually everything from a simple pair of applications to the most complex business environments, IBM MQ helps you improve business responsiveness, control costs, reduce risk—and gain real-time insight from mobile, IoT and sensor data.
There are no actively maintained images on Docker Hub. Instead, use IBM Container Registry:
icr.io/ibm-messaging/mq:9.3.2.0-r2
Tags and respective Dockerfile
links for images which are no longer actively maintained with security fixes, or use MQ versions which are no longer in support. You are recommended to avoid use of these images, but they are left for compatibility reasons, and may be withdrawn at any time:
9.2.4.0-r1
, latest
(Dockerfile)9.2.3.0-r1
, (Dockerfile)9.2.2.0-r1
, (Dockerfile)9.2.1.0-r1
, (Dockerfile)9.2.0.0-r2
(Dockerfile)9.2.0.0-r1
(Dockerfile)9.1.5.0-r2
All images are “Continuous Delivery” (CD) releases, and are available for download for up to one year (from 9.1.0.0 onwards), with new CD releases superseding older versions. If you want to use MQ V8.0.0 or V9.0.0, see this sample for how to build your own image.
License:
IBM MQ Advanced for Developers and Apache License 2.0. Note: The IBM MQ Advanced for Developers license does not permit further distribution and the terms restrict usage to a developer machine.
Where to get help:: IBM MQ Documentation
Where to file issues:
GitHub
Maintained by: IBM
Supported architectures:
amd64
, s390x
Run IBM® MQ Advanced for Developers in a container.
See the usage documentation for details on how to run a container.
Note that in order to use the image, it is necessary to accept the terms of the IBM MQ license by setting the LICENSE
environment variable.
accept
to agree to the MQ Advanced for Developers license. If you wish to see the license you can set this to view
.true
to generate Prometheus metrics for your Queue Manager.false
to stop the default objects being created.admin
user. Must be at least 8 characters long. Default is passw0rd
.DEV.APP.SVRCONN
channel to become secured and only allow connections that supply a valid userid and password. Must be at least 8 characters long. Default is blank (no password required) for MQ clients, and passw0rd
for HTTP clients.MQ_TLS_PASSPHRASE
. When enabled the channels created will be secured using the TLS_RSA_WITH_AES_128_CBC_SHA256
CipherSpec. Note: you will need to make the keystore available inside your container, this can be done by mounting a volume to your container.MQ_TLS_KEYSTORE
.See the default developer configuration docs for more information about the default developer configuration supported by the MQ Advanced for Developers image.
If you want to use IBM MQ in Kubernetes, you can find an example Helm chart here: IBM charts. You can find more information about using IBM MQ in Kubernetes here.
© Copyright IBM Corporation 2015, 2022
docker pull ibmcom/mq