-
Notifications
You must be signed in to change notification settings - Fork 186
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
Building a Centos/RHEL image on a Ubuntu OS fails with Use of rpm to install X is no longer supported
#166
Comments
sorry can you please advice if the is a way around this i just tried to install MQ 9.1 on linux ubuntu and getting the same problem using |
i tried reading the recommendation above but not understanding what needed to overcome this |
Hi @Roligucci - This issue describes a problem that users will encounter when trying to build the IBM MQ 9.1 Container image. From what you've described it looks like you're trying to just install IBM MQ 9.1 on a Virtual machine. A change was made in 9.1 to enforce using debian install files on debian based operating systems. As you're using an Ubuntu OS you must use the debian install files to install IBM MQ. You can find instructions for installing IBM MQ 9.1 using debian install files here. |
I'm little late to this, but I solved it faking temporarily uname output. Basically, the installation is based in the value from /usr/bin/uname. I just put a shell script in this location, installed the RPM and rolled-back the uname to its original place. RUN mv /usr/bin/uname /tmp/uname && \
echo '#!/bin/bash' > /usr/bin/uname && \
echo 'echo "Linux geeklab 3.10.0-693.21.1.el7.x86_64 #1 SMP Wed Mar 7 19:03:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"' >> /usr/bin/uname && \
chmod u+x /usr/bin/uname
RUN cd /root/MQServer && ./mqlicense.sh -accept && rpm -ivh MQSeriesServer-9.1.0-0.x86_64.rpm MQSeriesRuntime-9.1.0-0.x86_64.rpm
RUN mv /tmp/uname /usr/bin/uname |
I'm having a similar issue. Trying to build a RHEL docker container that uses IBM MQ on an Ubuntu machine is failing with:
This doesn't make sense to me, I'm installing into a RHEL container which uses rpm, so how could I possibly use any thing else? |
@lockieRichter, did you try the steps I put in the last comment? -- Of course it makes sense. Even if you're running a RHEL container, when you do The problem here is that IBM MQ tries to guess the current system based on uname, and the workaround I put in the last command mislead IBM MQ to think that we're actually in a RPM-based distribution. |
@juninho ahh I see what you're saying, I was getting mixed up between containers and VMs. I did try your suggested steps but they did not work for me. I'm not 100% sure why, so might have to try again... |
@lockieRichter, what exactly are you trying to do? What it is not working for you? -- EDIT: sorry, my fault... You need to use Try again, please... |
@juninho as I said, we are trying to build a RHEL container that uses IBM MQ and pymqi from an Ubuntu AWS server. When we try to build the docker image we get the message |
Symptoms
You have ran
make build-devserver
ormake build-advancedserver
on a ubuntu machine with a base image that is not ubuntu.Your build fails and you see the following error in the
install-mq.sh
outputThe text was updated successfully, but these errors were encountered: