This will enable use to chain/compose the component images into arbitrary ways. I think it will look like:
ARG base_image=exaworks/sdk-base
FROM $base_image
The first use-case would be our existing one: creating an image with a single component. Due to the default argument value, the existing build command will continue to work as-is: docker build -t rp docker/rp
The second use-case would be as for pair-wise integrations (two components) or a big monolithic image with all of the components. We could achieve this by "chaining" the images (e.g., sdk-base -> swift-t -> parsl -> rp -> flux).
This will enable use to chain/compose the component images into arbitrary ways. I think it will look like:
The first use-case would be our existing one: creating an image with a single component. Due to the default argument value, the existing build command will continue to work as-is:
docker build -t rp docker/rpThe second use-case would be as for pair-wise integrations (two components) or a big monolithic image with all of the components. We could achieve this by "chaining" the images (e.g.,
sdk-base->swift-t->parsl->rp->flux).