You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies if this has been asked before, but I can't find anything when I search the issues...
Is it possible to build an image that includes one or more specific APAR's? The MQ estate we manage runs on different platforms e.g. appliance, container, software. Periodically we have to request a custom LTS release with one or more APAR's included, which IBM is able to provide for appliance \ software. I am unsure how, or even if, we could do the same for a container image using the uninstalled .tar.gz package.
The text was updated successfully, but these errors were encountered:
If you get a full no-install package (e.g. for a fix release), then you can just build the container as normal with the replacement package. If you have an interim fix with just one or two patched files, then you can create a new Containerfile/Dockerfile to add an image layer on top of an existing image. For example:
FROM mymq:9.3.0.2-r1
COPY patched.dat /opt/mqm/bin/patched.dat
The file "patched.dat" is just an example here, but the resulting image would overwrite any files you needed. Just be mindful of file permissions, as you want to make sure that the "root" group (GID 0) has the correct permissions on the new file. You can see how this is managed in the Dockerfile-server from this repo.
Apologies if this has been asked before, but I can't find anything when I search the issues...
Is it possible to build an image that includes one or more specific APAR's? The MQ estate we manage runs on different platforms e.g. appliance, container, software. Periodically we have to request a custom LTS release with one or more APAR's included, which IBM is able to provide for appliance \ software. I am unsure how, or even if, we could do the same for a container image using the uninstalled .tar.gz package.
The text was updated successfully, but these errors were encountered: