Based on the discussion in the issue, I have restored the original behavior of the Dockerfile (with ENV definitions for the Geant4 data directories). These are unset manually in the entrypoint if a custom Geant4 build is used. I've also documented some of the things you need to know if you want to use different versions of Geant4 (e.g. G4 11). I also added a setting that lets you manually point the G4 data directory if you need to (e.g. for multiple builds with one common place for the data to save space).
Lastly, to make real sure that this feature is never used accidentally, the entrypoint will warn if the environment variable is used (similar to how the LDMX-sw cmake config warns for non-container builds). It can be silenced by defining yet another environment variable :)
Check List
[x] I successfully built the container using docker
[x] I was able to build ldmx-sw using this new container build
I can build ldmx-sw with both the built in Geant4, a custom Geant4 10.2.3 (debug build), and Geant4 11.2.0.
[x] I was able to test run a small simulation and reconstruction inside this container
... The Hcal test took 88 seconds but that... probably is a different issue...
I also ran an EcalPN config.
[x] I was able to successfully use the new packages. Explain what you did to test them below:
This updates the container to do some additional work to be able to support Geant4 builds other than 10.2.3. See https://github.com/LDMX-Software/docker/issues/83
Based on the discussion in the issue, I have restored the original behavior of the Dockerfile (with ENV definitions for the Geant4 data directories). These are unset manually in the entrypoint if a custom Geant4 build is used. I've also documented some of the things you need to know if you want to use different versions of Geant4 (e.g. G4 11). I also added a setting that lets you manually point the G4 data directory if you need to (e.g. for multiple builds with one common place for the data to save space).
Lastly, to make real sure that this feature is never used accidentally, the entrypoint will warn if the environment variable is used (similar to how the LDMX-sw cmake config warns for non-container builds). It can be silenced by defining yet another environment variable :)
Check List
... The Hcal test took 88 seconds but that... probably is a different issue...
I also ran an EcalPN config.