FredHutch/ls2_lmod

Name: ls2_lmod

Owner: Fred Hutchinson Cancer Research Center

Description: Lmod install for LS2

Created: 2018-01-25 22:31:32.0

Updated: 2018-01-25 22:35:23.0

Pushed: 2018-01-26 22:13:52.0

Homepage: null

Size: 10

Language: Shell

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

ls2_easybuild

Please look at ls2 for details on how to build these Dockerfiles and how to use them to deploy the same software to a local archive.

This container adds:

• Lmod with OS pkgs for lua dependencies

Building this container

Build this container with:

docker build . --tag fredhutch/ls2_lmod:7.7.14 --build-arg LMOD_VER=7.7.14

Note that LMOD_VER has no default value and not setting it will cause the build to fail.

Using this to deploy Lmod outside the container

If you want to use this container to deploy identically to a location outside the container, these are the steps:

1. Build the container normally
2. Run the container with the deploy script:
3. docker run -ti --rm -v <outside_vol>:<outside_vol> --user root fredhutch/ls2_lmod:<LMOD_VER> OUT_UID=<UID> OUT_GID=<GID> OUT_PREFIX=<PREFIX> /bin/bash /home/${LS2_USERNAME}/.ls2/deploy_lmod.sh

FAQ on the ls2 deploy step

Do I need to do this step?

No, once the initial container build is done, you have a container with the specified software pacakge(s) built and installed.

Why a second deploy step?

We use an NFS-mounted software volume to ensure our software is consistent across our HPC cluster and other Linux systems. This is the method we use to ensure the same software builds are present on our software volume and in ls2 containers.

Why do the outside_vol and “inside” outside_vol have to match?

Paths will be coded into the installed modulesfiles, so locations must be the same everywhere.

What are OUT_UID and stuff?

You will want the files written outside the container (in software volume) to be written by an owner and a group that make sense outside the container. Also, for collaboration (multiple builders if you choose), a common group is required. Note also that OUT_PREFIX and <outside_vol> must match

What about multiple builders (building under user accounts)?

You will want to have all builder accounts be members of the same group. That group should own your PREFIX (ex: /app) folder, and that folder should have the setgid bit set (ex: chmod g+s /app).

Ben, I work with you and just want to update this software package!

Ok, to simple update the software version, run these commands:

1. docker build . --tag fredhutch/ls2_lmod:<new_ver> --build-arg LMOD_VER=<new_ver>
2. docker push fredhutch/ls2_lmod:<new_ver>
3. docker run -ti --rm -v /app:/app --user root -e OUT_UID=${UID} OUT_GID=158372 fredhutch/ls2_lmod:<new_ver> /bin/bash /ls2/deploy_lmod.sh

This runs the successfully built ls2_lmod container with our /app mounted, and then installs Lmod as the OUT_UID with group OUT_GID to preserve permissions in /app. It also configures and updates the system cache.