If at some point the container should be able to run on a batch queue, it would be easiest for all running containers to share a cache. If not, they'd have to run without a mounted cache, which seems like a waste of resources.
Can CVMFS handle multiple instances writing to the same cache? If not, what can I do? Images with larger prefilled caches for batch running?
This is where an external CVMFS comes in handy even with just one container! Run a CVMFS-container to provide the volume, then use have images (possibly without cvmfs) that mount the cvmfs dir readonly via docker.
If at some point the container should be able to run on a batch queue, it would be easiest for all running containers to share a cache. If not, they'd have to run without a mounted cache, which seems like a waste of resources.
Can CVMFS handle multiple instances writing to the same cache? If not, what can I do? Images with larger prefilled caches for batch running?