Re: module load inside rpmbuild inside docker

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, May 4, 2019 at 5:30 AM Neal Gompa <ngompa13@xxxxxxxxx> wrote:
>
> On Sat, May 4, 2019 at 7:26 AM Daniel Walsh <dwalsh@xxxxxxxxxx> wrote:
> >
> > On 5/3/19 6:00 PM, Christoph Junghans wrote:
> > > Hi,
> > >
> > > I wanted to bump the legion package to 19.04.0
> > > (https://bugzilla.redhat.com/show_bug.cgi?id=1705033), however for
> > > some reason all tests segfault with openmpi
> > > (https://koji.fedoraproject.org/koji/taskinfo?taskID=34577005), so I
> > > reported this upstream
> > > (https://github.com/StanfordLegion/legion/issues/533) and included a
> > > minimal dockerfile to reproduce this issue:
> > >
> > > FROM fedora:rawhide
> > > RUN dnf install -y spectool wget rpm-build dnf-plugins-core
> > > RUN wget https://src.fedoraproject.org/fork/junghans/rpms/legion/raw/master/f/legion.spec
> > > RUN spectool -g legion.spec
> > > RUN dnf builddep -y legion.spec
> > > RUN dnf install -y make
> > > RUN rpmbuild -D"_sourcedir ${PWD}" -D"_srcrpmdir ${PWD}" -ba legion.spec
> > >
> > > This worked fine on Thursday(?) to reproduce the failing tests in
> > > %check, but now rpmbuild fails at an earlier stage with:
> > > + module load mpi/mpich-x86_64
> > > ++ /usr/share/lmod/lmod/libexec/lmod sh load mpi/mpich-x86_64
> > > Lmod has detected the following error: The following module(s) are unknown:
> > > "mpi/mpich-x86_64"
> > >
> > > If I jump into the container interactively (docker run -it ..
> > > /bin/bash), "module load" as well as rpmbuild (and "module load"
> > > inside) works.
> > >
> > > If know this is a convoluted case, but any ideas how fix this?
> > >
> > > Christoph
> > >
> > >
> > Are you running a privileged container in one case and not in the
> > other.  Normal running of containers should not allow you to load a
> > kernel module.
> >
> >
> > BTW Have you tried this with Podman?
>
> I'm pretty sure these aren't kernel modules, but environment modules
> for OpenMPI and such...
Correct.

I am thinking there is something missing in the default environment in
the container, that gets loaded in the interactive mode.

Christoph
>
>
>
> --
> 真実はいつも一つ!/ Always, there's only one truth!
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx



-- 
Christoph Junghans
Web: http://www.compphys.de
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux