Skip to content
Snippets Groups Projects
Select Git revision
  • 33727caf4c3424a5ba5e55ee9d5f5b24bbbb4253
  • master default protected
  • script_devel
  • parallel_trapping
  • offload_trapping
  • unify_iterations
  • containers-m10
  • magma_refinement
  • release9
  • enable_svd
  • parallel_angles_gmu
  • containers-m8
  • parallel_angles
  • profile_omp_leonardo
  • test_nvidia_profiler
  • containers
  • shaditest
  • test1
  • main
  • 3-error-in-run-the-program
  • experiment
  • NP_TMcode-M10a.03
  • NP_TMcode-M10a.02
  • NP_TMcode-M10a.01
  • NP_TMcode-M10a.00
  • NP_TMcode-M9.01
  • NP_TMcode-M9.00
  • NP_TMcode-M8.03
  • NP_TMcode-M8.02
  • NP_TMcode-M8.01
  • NP_TMcode-M8.00
  • NP_TMcode-M7.00
  • v0.0
33 results

docker

Name Last commit Last update
..
dockerstuff/intelcomps
Dockerfile
README.md
README.md

Docker support for the NP-TMcode project

This Dockerfile allows to create mainly:

  • the np-tmcode image that is used by the gitlab pipeline runner to test compile and execution of requested merges
  • the np-tmcode-run image, that contains only the pre-built executables, python test scripts, compiled documentation, and the minimal runtime to run them

In order for the docker build to correctly set the context, so that it can access the directories containing source codes, docker build must be invoked from this directory as:

docker build -f Dockerfile ../.. --target <image name>

where <image name> is either np-tmcode or np-tmcode-run. One may also add the docker build option -t tagname to specify the tagname the built image should have in his/her registry.