Should GMT copy or mount the repository

[ArneTR]

At the moment the repository to be measured with ScenarioRunner in GMT will be mounted to /tmp/repo

This is the most efficient way to make the repository available to the measurement. However in order to safeguard the host system the repository is mounted read-only.

If some operations need to be done on the data like for instance an npm install or similar the operation fails.

The easy solution is to copy the repository to a different location inside of the container and then executing the npm install (or whatever else) again.

The main question to the community:

• Should GMT directly copy the repository into the container instead of just mounting it?

We believe this would increase unneeded copies and especially if repos get very large also consume duplicate disk space etc.

We currently see about 97% of all runs not needing to copy the repository after it was mounted but executing commands directly on the read-only copy. However our view might be biased as we never see people failing to use the GMT as they fail at this particular hurdle.

Happy for any feedback on this!

[ribalba]

I am part of the we ;)