To design a strategy around storing and deploying local containers on Setonix

PawseySC / pawsey-spack-config

Automated deployment system for the scientific software stack in use at Pawsey

BSD 3-Clause "New" or "Revised" License

4 stars 9 forks source link

To design a strategy around storing and deploying local containers on Setonix #187

Open dipietrantonio opened 1 year ago

dipietrantonio commented 1 year ago

Pawsey develops and deploys several containers such as OpenFOAM containers, Tensorflow (built on top of the AMD one to fix some missing packages), and some others. For those containers that are not published on a remote server such as DockerHub, I suggest defining a local, staff-managed repository on the /software filesystem. Then, SHPC recipes can refer to that location.

A good location would be /software/setonix/container-images.

marcodelapierre commented 1 year ago

Very good idea! My suggestion is to also scope which images will not be pushed to the public repo, and hence need the dedicated local storage area. (e.g. closed source/licensed software...)

marcodelapierre commented 1 year ago

Another suggestion, from original conversations with Maciej and others within Pawsey: keep the scope of officially supported images small (base images, strategic support cases, ..), to maintain amount of work manageable