IBM MQ Advanced for Developers container image
A prebuilt container image is available for IBM® MQ Advanced for Developers. This image is available from the IBM Container Registry. This image is suitable for use with Docker, Podman, Kubernetes, and other container environments.
Available images
IBM MQ images are stored in the IBM Container Registry:
- IBM MQ Advanced for Developers 9.3.0.17: icr.io/ibm-messaging/mq:9.3.0.17-r1
- IBM MQ Advanced for Developers 9.3.5.1: icr.io/ibm-messaging/mq:9.3.5.1-r1
Quick reference
- License:
- IBM MQ Advanced for Developers and Apache License 2.0. Note that the IBM MQ Advanced for Developers license does not permit further distribution, and the terms restrict usage to a developer machine.
- Where to file issues:
- Available for the following CPU architectures:
- amd64
- s390x
- ppc64le
Usage
Run IBM MQ Advanced for Developers in a container.
See the usage documentation for details on how to run a container.
To be able to use the image, you must accept the terms of the IBM MQ license by setting the LICENSE environment variable.
Environment variables supported
- LANG
- Set the language you want the license to be printed in.
- LICENSE
- Set accept to agree to the IBM MQ Advanced for Developers license conditions.
- LOG_FORMAT
- DEPRECATED: Superseded by MQ_LOGGING_CONSOLE_FORMAT.
- MQ_ADMIN_PASSWORD
- Specify the password of the admin user.
- MQ_APP_PASSWORD
- Specify the password of the app user.
- MQ_DEV
- Set false to stop the default objects being created.
- MQ_ENABLE_METRICS
- Set true to generate Prometheus metrics for your queue manager.
- MQ_LOGGING_CONSOLE_SOURCE
- Specify a comma-separated list of sources for logs that are mirrored to the container's stdout location.
- MQ_LOGGING_CONSOLE_FORMAT
- Replaces LOG_FORMAT.
- MQ_LOGGING_CONSOLE_EXCLUDE_ID
- Specify a comma-separated list of message IDs for log messages that are excluded.
- MQ_QMGR_NAME
- Set the name you want your queue manager to be created with.
For more information about the default developer configuration supported by the IBM MQ Advanced for Developers image, see the default developer configuration documentation.
Example queue manager YAML that describes how to specify passwords for admin and app users.
From IBM MQ 9.3.4, the admin and
app user IDs no longer have default passwords. For these users, you must
provide passwords when deploying a queue manager using the Development
license.
Here is an example queue manager YAML that shows you how to do this with the IBM MQ Operator.
oc create secret generic my-mq-dev-passwords --from-literal=dev-admin-password=passw0rd --from-literal=dev-app-password=passw0rd
apiVersion: mq.ibm.com/v1beta1
kind: QueueManager
metadata:
name: qm-dev
spec:
license:
accept: false
license: L-AXAF-JLZ53A
use: Development
web:
enabled: true
template:
pod:
containers:
- env:
- name: MQ_DEV
value: "true"
- name: MQ_CONNAUTH_USE_HTP
value: "true"
- name: MQ_ADMIN_PASSWORD
valueFrom:
secretKeyRef:
name: my-mq-dev-passwords
key: dev-admin-password
- name: MQ_APP_PASSWORD
valueFrom:
secretKeyRef:
name: my-mq-dev-passwords
key: dev-app-password
name: qmgr
queueManager:
storage:
queueManager:
type: persistent-claim
name: QUICKSTART
version: 9.3.5.1-r1