From 3ad3e7ea1677b9c360aa05cabf32c7e6206e0867 Mon Sep 17 00:00:00 2001 From: "arthur.barr@uk.ibm.com" Date: Wed, 13 Apr 2022 14:15:29 +0100 Subject: [PATCH] Use icr.io in usage doc --- docs/usage.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/usage.md b/docs/usage.md index d1c503a..c8a5cea 100644 --- a/docs/usage.md +++ b/docs/usage.md @@ -14,7 +14,7 @@ docker run \ --publish 1414:1414 \ --publish 9443:9443 \ --detach \ - ibmcom/mq + icr.io/ibm-messaging/mq ``` ## Running with the default configuration and a volume @@ -34,7 +34,7 @@ docker run \ --publish 9443:9443 \ --detach \ --volume qm1data:/mnt/mqm \ - ibmcom/mq + icr.io/ibm-messaging/mq ``` The Docker image always uses `/mnt/mqm` for MQ data, which is correctly linked for you under `/var/mqm` at runtime. This is to handle problems with file permissions on some platforms. @@ -51,7 +51,7 @@ docker run \ --publish 9443:9443 \ --publish 9157:9157 \ --detach \ - ibmcom/mq + icr.io/ibm-messaging/mq ``` ## Customizing the queue manager configuration @@ -67,7 +67,7 @@ Note that a listener is always created on port 1414 inside the container. This The following is an *example* `Dockerfile` for creating your own pre-configured image, which adds a custom MQ configuration file: ```dockerfile -FROM ibmcom/mq +FROM icr.io/ibm-messaging/mq USER 1001 COPY 20-config.mqsc /etc/mqm/ ```