5a18280057
* Updated UBI to UBI8 * Updated the README to include the redhat login * Updated to use non-deprecated registry * Added sed filter into docker file to remove ubi7 * Added automatic login into the makefile based on env variables, also removed nodocs from mq-explorer * Minor typo fix
2.5 KiB
Building a container image
Prerequisites
You need to have the following tools installed:
If you are working in the Windows Subsystem for Linux, follow this guide by Microsoft to set up Docker first.
You will also need a Red Hat Account to be able to access the Red Hat Registry.
Building a production image
This procedure works for building the MQ Continuous Delivery release, on amd64, ppc64le and s390x architectures.
- Create a
downloadsdirectory in the root of this repository - Download MQ from IBM Passport Advantage or IBM Fix Central, and place the downloaded file (for example,
IBM_MQ_9.1.3_LINUX_X86-64.tar.gz) in thedownloadsdirectory - Login to the Red Hat Registry:
docker login registry.redhat.iousing your Customer Portal credentials. - Run
make build-advancedserver
Warning
: Note that MQ offers two different sets of packaging on Linux: one is called "MQ for Linux" and contains RPM files for installing on Red Hat Enterprise Linux and SUSE Linux Enterprise Server; the other is for Ubuntu. The MQ container build uses a Red Hat Universal Base Image, so you need the "MQ for Linux" RPM files.
If you have an MQ archive file with a different file name, you can specify a particular file (which must be in the downloads directory). You should also specify the MQ version, so that the resulting image is tagged correctly, for example:
MQ_ARCHIVE=mq-1.2.3.4.tar.gz MQ_VERSION=1.2.3.4 make build-advancedserver
Building a developer image
Login to the Red Hat Registry: docker login registry.redhat.io using your Customer Portal credentials.
Run make build-devserver, which will download the latest version of MQ Advanced for Developers from IBM developerWorks. This is currently only available on the amd64 architecture.
You can use the environment variable MQ_ARCHIVE_DEV to specify an alternative local file to install from (which must be in the downloads directory).
Installed components
This image includes the core MQ server, Java, language packs, GSKit, and web server. This can be configured by setting the MQ_PACKAGES argument to make.