...
Applications. You will need your docker image name/URL or a proprietary application name, your input files, and the command line to execute within the executed environment. The command line can be as simple as executing an application with a docker image, a command to execute the first input file, or a more involved script that handles the logic of your job.
Execution Environments. It's possible to run code in a range of languages directly on Charity Engine, by specifying the relevant execution environment.
Input+Output Files and Networking. All nodes have limited network access for retrieving input data via files submitted during job/batch creation and/or from internet resources available via HTTP(S).
...
- Docker images available on Docker Hub (e.g.
docker:python:3.7) - Custom Docker images available anywhere online (e.g.
docker:image-name https://example.com/filefor 64bit docker images, ordocker-x86:image-name https://example.com/filefor 32bit docker images) - Proprietary applications Applications deployed directly on the Charity Engine network, both open-source and proprietary (e.g.
charityengine:wolframengine). For a list, see our App Library.
See instructions on the appropriate interface (section 1.1) for further execution details.
Execution Environments
To run raw code on Charity Engine, just upload your code and specify the relevant execution environment, either using a "named" environment in our App Library, or by specifying an appropriate container on Docker Hub or the web (see 1.2 "Applications", above)
...
Examples:
See instructions on the appropriate interface (section 1.1) for further execution details.
Input + Output Files
Once the computation environment runs, the input files provided during job submission are downloaded from the internet and are made available for the applications on the compute nodes in the /local/input virtual disk location.
...