* Adding docker-compose
Adding docker-compose configuration file to define how containers
should be linked and what data to share.
Adding setenv files to the hcc containers
* New templating engine to generate dockerfiles on disk
Changing roc-setup script to generate dockerfiles, so
images are built with build contexts. Now, roc-setup only
generates dockerfiles, and leverages the docker-compose utility to
build images and compose the shared volumes
* Adding thunk and runtime to docker compose file
Building the thunk and runtime components with docker
compose. Refactoring of various template files.
* Further docker-compose development
Added lots of little features and refactorings
1. Eliminated remove-image and dry-run options from roc-setup as
redundant
2. Templated the install location of volumes
3. Rewrote the README file
4. Fixes to the install procedure for ROCT
* Extracting binary hsa libraries, adding kfd device passthrough
HSAIL generated binaries need libraries available in the ROCR debian
package to properly function.
The docker-compose yaml file now passes /dev/kfd access through to the
container
Various cleanup of docker template files
* docker-compose.yml.template fix
The image names for the example rocm-project services were the
same
The ROC infrastructure has a few permutations that are useful
in different circumstances. Namely, the branch to build source from
and the build configuration. Instead of creating seperate dockerfiles
for each variant, which could explode, the setup script has been
changed into a templating engine, wherin it transforms a docker template
file into a real dockerfile by substituting keywards. It is similar
to a pre-processor for the dockerfiles.
