Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Queries #536

Open
Murali-Cloudbridge opened this issue Oct 11, 2023 · 1 comment
Open

Queries #536

Murali-Cloudbridge opened this issue Oct 11, 2023 · 1 comment

Comments

@Murali-Cloudbridge
Copy link

How to install any packages that we might need on the container itself. For instance, we might want to install git or jq command line tool to run some configuration scripts. Do we have access to the root user on the container itself to do this?

The current solution uses IBM MQ Advanced for the Developer's container image. How do we change it to use the IBM MQ Advanced production image? Does this require a complete cluster rebuild, or can the image be switched without the rebuild?

@arthurbarr
Copy link
Member

You can add packages to the list of extra packages which get installed (this script is called as part of the Dockerfile):

EXTRA_RPMS="bash bc ca-certificates file findutils gawk glibc-common grep ncurses-compat-libs passwd procps-ng sed shadow-utils tar util-linux which"

For a production image, you need to build your own image, which could be based on this sample if you wish. MQ Advanced and MQ Advanced for Developers have different installation media, so you can't switch between them with configuration. If you are using the MQ Operator on Red Hat OpenShift Container Platform, then pre-built images are available for each.

JEFFLUFC added a commit that referenced this issue Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants