-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: Add CentOS 7 based Dockerfile #7
Conversation
matthewfeickert
commented
Jun 4, 2021
•
edited
Loading
edited
- Resolves Make Blue Waters compatible Docker image #4
- Resolves Enable devtools in CentOS based Docker images by default #8
Seems that a more modern version of boost is required
|
Hi, even though active development has stopped, we do try to provide minimal support. This is strange, as it has been developed on CentOS 7, and some people are using it on CentOS 7 as we speak (@FlorianBury). What is the error message? |
d39093e
to
48ace21
Compare
🙇 Awesome and thank you!
Ah that's actually quite good to know. I've only been able to get things to build with installing BOOST from source and then installing
At the moment I don't have a particular build error message, but I was getting situations where running the tests I've setup (the MoMEMta tutorial in the build image) would just run for over an hour without converging. I'm making some changes to the underlying base images I'm building on, so I'm going to see if that resolves things. |
need to treat /usr/local/venv/ as the base for anything that has python bindings to get it to be seen and known to the virtual environment
Hi @matthewfeickert, On my side I built MoMEMta from sources, using the following cvmfs modules
I am working as we speak with this setup and it works fine. |
Yes I remember we had some issues because depending on the version, ROOT forces using exactly the same C++ standard as it was built with...
The system provided environment modules with more recent GCC and BOOST versions. Which is another way to say they were built from source (just not by us)! That being said, I've tried to build with recent GCC10 and ROOT 6.22 and it fails. I'm looking into it. |
Could you perhaps try pulling MoMEMta from https://github.com/swertz/MoMEMta/tree/cuba-4.2.1 ? With this branch I manage to run an example on CentOS with GCC10 and ROOT 6.22 (with |
Yeah, the problem with CVFMS is that it is like the world's biggest virtual environment with special cases — there are plenty of modules that exist on it that you can't easily get setup with the same configurations outside. But this is at least a helpful listing of versions to have — thanks @FlorianBury.
Ah this is good to know, given that I currently have ROOT being built with
I can rebuild the ROOT docker image with
At the moment the build for
Yeah, once I rebuild the |
I've tried building and installing the examples from the Tutorials as in your test setup, using the GCC10/ROOT622 build on COS7, and it finishes running in a few minutes. I'm not sure if this is really because of something that was changed between v1.0.0 and the master, or between the master and my cuba-4.2.1 branch... But if you manage to get it work using that branch I'm happy to merge it and tag a bugfix release that could pull! |
Thanks! This is all useful info. I'll use this as some guides for debugging and hopefully be able to provide some example failing and working workflows later on today. |
Btw, looking at your test job output, the example runs an infinite loop when iterating over the events:
Which would point to an issue with the ROOT/TTreeReader setup rather than with MoMEMta itself...? |
@swertz I have things working now that I've rebuilt the ROOT base image with I've also built against your fork's |
Thanks for checking! Good that it is solved 👍 I have added a note about the C++ standard in the README and a v1.0.1 tag to MoMEMta that you can pull in your container images: https://github.com/MoMEMta/MoMEMta/releases/tag/v1.0.1 |
Fantastic! Thank you very much @swertz. |