Jacob Faibussowitsch <[email protected]> writes: > 2. (More a question for Jed) If I am using Jeds docker image anyways and we > have CI/CD builds also using his docker images (correct me if I am wrong > here) and a valgrind build in stage 3 why not include those build arguments > in the MPICH included in the images? I think the valgrind build for CI/CD > actually downloads and builds MPICH through petsc configure, is this because > of the errors I detailed below?
I'd welcome a PR to add options like --enable-g=meminit. I'd rather not make that general-purpose image use ch3:sock because people also use it (via Singularity or Shifter) for performance. We could make a different Docker image with ch3:sock.
