Currently Cerberus reads the containr profiles in the file profiles/container-default.json. When custom configuration files are used, the profiles are defined there. Check how to use the custom configuration files for such cases.
A container profile is a json object with a field id, which is used by the container and UI module to handle resource allocation. A container profile currently supports the following set of fields:
cpu_count- amount of cpus allowed for a taskgpu_count- amount of gpus allowed for a taskmem_limit- maximum amount of RAM the task can use before being terminatedenable_network- allow the tool to have a network connection to the outside world, i.e. calling an external service