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

install EasyBuild as a module in base image + clean up GCC 9.3.0 image #8

Merged
merged 5 commits into from
May 29, 2020
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 14 additions & 2 deletions containers/Dockerfile.base-centos7
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,13 @@ ARG EB_VER=4.2.1
LABEL easybuild_version=${EB_VER}
# install required packages (EPEL is required for Lmod)
RUN yum install -y epel-release \
&& yum install -y bzip2 file gcc-c++ git Lmod make openssl-devel patch python3-pip unzip vim which
&& yum install -y bzip2 file gcc-c++ git Lmod make openssl openssl-devel patch python3-pip unzip vim which rdma-core-devel
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we install rdma-core-devel here? Who is to say someone wants to run RDMA stuff

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having rdma-core-devel installed affects how OpenMPI is configured (--with-verbs or --without-verbs).

I'm happy to remove it, it's probably overkill here, but I don't think it hurts to have it installed?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just wonder if we need to install this in the base - but ok... premature optimization I'd say

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, I don't think it hurts much, except for size of the container a little bit?

Stripping it out is not a huge deal for the tutorial, and if it's there you can add rdma-core-devel in another image on top of this one, and rebuild OpenMPI (and everything that depends on it...), if you really want IB support, but that's a hassle.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's keep it for now... and put a pin in it for a later discussion

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Open an issue on it in this repo

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#10

# install EasBuild & archspec
RUN pip3 install easybuild==${EB_VER} archspec
# add 'easybuild' user
RUN useradd -ms /bin/bash easybuild
# create /scratch & /easybuild directories
RUN mkdir /scratch && chown easybuild:easybuild /scratch && mkdir /easybuild && chown easybuild:easybuild /easybuild
boegel marked this conversation as resolved.
Show resolved Hide resolved
# define $EB_PYTHON to ensure EasyBuild runs with python3
ENV EB_PYTHON=python3
# Define the ENTRYPOINT for subsequent commands (CMD)
Expand All @@ -19,5 +21,15 @@ SHELL ["/bin/bash", "-l", "-c"]
CMD ["bash"]
# switch to 'easybuild' user
USER easybuild
# install EasyBuild as a module (& clean up /scratch)
RUN eb --install-latest-eb-release --prefix /scratch --installpath /easybuild && rm -rf /scratch/*
# print info on Lmod & EasyBuild
RUN ml --version && which -a eb && eb --version & eb --show-system-info
RUN ml use /easybuild/modules/all && ml EasyBuild && ml --version && which -a eb && eb --version & eb --show-system-info
# remove globally installed EasyBuild, we can use the module going forward
USER root
RUN pip3 uninstall -y easybuild
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

potential optimization #11

# switch to 'easybuild' user
USER easybuild
WORKDIR /home/easybuild
# disable output buffering in Python, so we see EasyBuild output as it progresses
ENV PYTHONUNBUFFERED=TRUE
boegel marked this conversation as resolved.
Show resolved Hide resolved
18 changes: 1 addition & 17 deletions containers/Dockerfile.centos7-GCC-9.3.0
Original file line number Diff line number Diff line change
Expand Up @@ -10,24 +10,8 @@ RUN export HOST_CPU_ARCH=$(python3 -c 'import archspec.cpu; print(archspec.cpu.h
# use $CPU_ARCH to define label and set it as environment variable (to use in subsequent builds
LABEL cpu_arch=${CPU_ARCH}
ENV CPU_ARCH=${CPU_ARCH}
# for example: docker build --build-arg CPU_ARCH=haswell
# create /scratch & /easybuild directories
USER root
RUN mkdir /scratch && chown easybuild:easybuild /scratch
RUN mkdir /easybuild && chown easybuild:easybuild /easybuild
USER easybuild
# use /easybuild for everything that should persist in the container (software, modules and sources)
# everything else goes in /scratch, which will be cleaned out
ENV EASYBUILD_PREFIX=/scratch
ENV EASYBUILD_INSTALLPATH=/easybuild
ENV EASYBUILD_SOURCEPATH=/easybuild/sources
# disable output buffering in Python, so we see EasyBuild output as it progresses
ENV PYTHONUNBUFFERED=TRUE
# install software & accompanying modules
RUN eb GCC-9.3.0.eb --robot --trace \
RUN eb --prefix /scratch --installpath /easybuild GCC-9.3.0.eb --robot --trace \
# clean up everything in /scratch
&& rm -rf /scratch/*
# finalize /easybuild, no changes can be made in /easybuild that persist!
VOLUME /easybuild
# make sure we start in /home/easybuild rather than / when shell in started in container
WORKDIR /home/easybuild