Public | Automated Build

Last pushed: a month ago
Short Description
IBM® MQ Advanced for Developers
Full Description

Supported tags and respective Dockerfile links

  •, 9, latest (Dockerfile) - available until July 2019
  • (Dockerfile) - available until November 2018 (updated date)

All images are “Continuous Delivery” (CD) releases, and are available for download for up to one year (from 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.

The 9 tag is deprecated.

Quick reference


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.

Environment variables supported by this image

  • LICENSE - Set this to accept to agree to the MQ Advanced for Developers license. If you wish to see the license you can set this to view.
  • LANG - Set this to the language you would like the license to be printed in.
  • LOG_FORMAT - Set this to change the format of the logs which are printed on the container's stdout. Set to - "json" to use JSON format (JSON object per line); set to "basic" to use a simple human-readable format. Defaults to "basic".
  • MQ_QMGR_NAME - Set this to the name you want your Queue Manager to be created with.
  • MQ_ENABLE_METRICS - Set this to true to generate Prometheus metrics for your Queue Manager.
  • MQ_DEV - Set this to false to stop the default objects being created.
  • MQ_ADMIN_PASSWORD - Changes the password of the admin user. Must be at least 8 characters long. Default is passw0rd.
  • MQ_APP_PASSWORD - Changes the password of the app user. If set, this will cause the 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_KEYSTORE - Allows you to supply the location of a PKCS#12 keystore containing a single certificate which you want to use in both the web console and the queue manager. Requires 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_PASSPHRASE - Passphrase for the keystore referenced in 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. This can be used to run the container on a cluster, such as IBM Cloud Private or the IBM Cloud Kubernetes Service.


© Copyright IBM Corporation 2015, 2018

Docker Pull Command
Source Repository