Support for mounting /code directory read-write when analyzing?

[lizalc]

As shown in lib/cc/analyzer/engine.rb line 84 the code volume (mapped to /code in the analyzer) is mounted read-only. This prevents the usage of analyzers which need to generate extra files when performing analysis. For me personally, this prevents the use of the MISRA add-on when analyzing C code with cppcheck via a slightly modified version of the codeclimate-cppcheck analyzer. The MISRA add-on works by having cppcheck generate additional .dump files of the code and then using the .dump files to perform the MISRA analysis.

Currently I'm working around this by generating the .dump files in an action that runs before my Code Climate cppcheck action that way the .dump files are present in the /code directory before analysis is performed. This isn't completely ideal though since have to manage two separate cppcheck actions.

Would it be feasible to allow the /code directory to be mounted read-write when running certain analyzers? Maybe via a user config option or some other method?

Some other discussion is here in the codeclimate-cppcheck repo: antiagainst/codeclimate-cppcheck#41