Just a quick question.. Is there a best practice for getting epel in to a ubi8 container? I'm trying to do this with yum -y install and the epel url. Do I need to enable anything else?
On 11/5/19 9:24 AM, bryan.hepworth@gmail.com wrote:
Just a quick question.. Is there a best practice for getting epel in to a ubi8 container?
I'm trying to do this with yum -y install and the epel url. Do I need to enable anything else? _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Not really something we cover with Podman. Scott, can you answer this one?
On Tue, Nov 5, 2019 at 9:39 AM Daniel Walsh <dwalsh@redhat.com> wrote:
On 11/5/19 9:24 AM, bryan.hepworth@gmail.com wrote:
Just a quick question.. Is there a best practice for getting epel in to a ubi8 container?
I'm trying to do this with yum -y install and the epel url. Do I need to enable anything else?
That works. There's not really a better way. You need to get the repo file included somehow, and either that or doing it via copying a local repo file in an image build works fine. If you want to then use that as a base image for other container builds that need content from EPEL, you can build that image and use it in the FROM line for any subsequent containers. josh
Bryan, Short answer is mileage may vary. See question #21 here: https://developers.redhat.com/articles/ubi-faq/#resources Best Regards Scott M On Tue, Nov 5, 2019 at 9:47 AM Josh Boyer <jwboyer@redhat.com> wrote:
On Tue, Nov 5, 2019 at 9:39 AM Daniel Walsh <dwalsh@redhat.com> wrote:
On 11/5/19 9:24 AM, bryan.hepworth@gmail.com wrote:
Just a quick question.. Is there a best practice for getting epel in to a ubi8 container?
I'm trying to do this with yum -y install and the epel url. Do I need
to enable anything else?
That works. There's not really a better way. You need to get the repo file included somehow, and either that or doing it via copying a local repo file in an image build works fine.
If you want to then use that as a base image for other container builds that need content from EPEL, you can build that image and use it in the FROM line for any subsequent containers.
josh
-- -- Scott McCarty, RHCA Product Management - Containers, Red Hat Enterprise Linux & OpenShift Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com Have you ever wondered what happens behind the scenes when you type www.redhat.com into a browser and hit enter? https://www.redhat.com/en/blog/what-happens-when-you-hit-enter
Thanks Scott I'd spied the note about epel elsewhere, but am determined to work through things. We use epel for R amongst other things and have done so for years reliably. The 8.1 release is making me change how we provide software to researchers and do this via containers.
Thanks Josh. I'm working through a few things and want to get everything to be based on ubi8
Hi All For the sake of completeness I got this to work locally by enabling a couple of repositories. It all worked seamlessly after that for installing R. FROM registry.access.redhat.com/ubi8/ubi RUN yum -y update && yum -y install yum-utils && yum-config-manager --enable rhel-8-for-x86_64-supplementary-rpms && yum-config-manager --enable codeready-builder-for-rhel-8-x86_64-rpms && yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm && yum -y install R-core-devel R-devel R This is on a registered local machine. it can't be built in quay.io like this, and I'm wondering if this also isn't allowed with that ubi8 image in quay.io in a public repository. R is one of the many building blocks we use for genetic analysis, and I'm keen to share information like this. Bryan
Bryan, Yeah, I did a quick test. In a nutshell, we won't be able to support this use case in UBI any time soon because it pulls in about 500 more packages from RHEL. I just did a quick test, but I still don't know how many of those are already in the UBI package set (I suspect a lot of them). So, today you are right, these images would not be redistributable. You could share Containerfiles and have people build them locally as a multi-stage build on a subscribed system, but regrettably, you couldn't push them to quay.io. Best Regards Scott M On Tue, Nov 26, 2019 at 8:42 AM <bryan.hepworth@gmail.com> wrote:
Hi All
For the sake of completeness I got this to work locally by enabling a couple of repositories. It all worked seamlessly after that for installing R.
FROM registry.access.redhat.com/ubi8/ubi RUN yum -y update && yum -y install yum-utils && yum-config-manager --enable rhel-8-for-x86_64-supplementary-rpms && yum-config-manager --enable codeready-builder-for-rhel-8-x86_64-rpms && yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm && yum -y install R-core-devel R-devel R
This is on a registered local machine. it can't be built in quay.io like this, and I'm wondering if this also isn't allowed with that ubi8 image in quay.io in a public repository.
R is one of the many building blocks we use for genetic analysis, and I'm keen to share information like this.
Bryan
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
-- -- Scott McCarty, RHCA Product Management - Containers, Red Hat Enterprise Linux & OpenShift Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com Deeply understand the different between Portability, Compatibility, and Supportability with containers: http://bit.ly/2Qw3dJI
participants (4)
-
bryan.hepworth＠gmail.com -
Daniel Walsh -
Josh Boyer -
Scott McCarty