chore: add basic Dockerfile

[imrn99]

Description

I used fastiron's file as reference: https://github.com/cea-hpc/fastiron/blob/main/Dockerfile

I adjusted it to:

• automatically clone the repo before build. That way we can restrict space mount to an "out dir"
• clone the repo I use to store input files
• remove the path installation since we're working with many binaries/benchmarks
• use a base with more features for the final image. I want to use the docker in interactive mode, so having a working shell is nice

TODO: test it

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.17%. Comparing base (6e38028) to head (183d06f).
Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #270      +/-   ##
==========================================
+ Coverage   85.14%   85.17%   +0.03%     
==========================================
  Files          62       63       +1     
  Lines        8924     9073     +149     
==========================================
+ Hits         7598     7728     +130     
- Misses       1326     1345      +19     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cedricchevalier19]

It is not totally clear to me what is the goal of this container.

If it is to provide a functional image for the end-user, the location is ok, if it is more for development and benchmarking, I think putting the file elsewhere or renaming it to benchmark.dockerfile or something like that is better.

[cedricchevalier19]

I have mixed feelings about this. If you want to create a container to bench the current branch you are one, it will not do.
Plus, it will not work if you are not connected to github .

I think accessing or copying the current repository into the builder makes more sense. You can use "COPY" or "RUN --mount" (see https://docs.docker.com/reference/dockerfile/#run---mount).

[imrn99]

I switched to binaries install due to issues with generated images

[cedricchevalier19]

For this one, you can use ADD to download and decompress the tarball from github. This way git is not required anymore.

[imrn99]

it seems like ADD timeouts on git links from my trials

[cedricchevalier19]

Does not having the source code available a problem here?

[imrn99]

see global comment

[imrn99]

I updated the file to be closer to how fastiron's one worked. I think you're right, it will be easier to generate some binaries + mount the repo for the rest of the files.

the perf install didn't work though, I think there is a version incompatibility. If that's ok I will fix it later, when we need actual profiling instead of exec times.

[cedricchevalier19]

I still think that a more precise name like benchmarks.dockerfile makes more sense.

[imrn99]

I still think that a more precise name like benchmarks.dockerfile makes more sense.

oh ok, I thought this point was related to the original content. I renamed the file