Closed sbinet closed 9 years ago
this would address issues like #5
commit hepsw/cubie@322e96442f1d8ea1f5701d9f4ac048c76183a424 provides a way to run multiple commands from within a container.
commit hepsw/docks@bba7282fccae037f201302a95825882b76c5ce99 leverages this for cvmfs-{base,atlas,cms,lhcb,lsst}
the multiple PODs + VOLUME
approach doesn't seem like doable for cvmfs.
cubied
works.
containers needing a daemon running (e.g.
sshd
,cvmfsd
) for correctly exposing or using resources have been relying on.bashrc
running a set of scripts (which in turn launch the daemons).this is very fragile. but containers can't easily run multiple programs (at least that's not the recommanded way of using
docker
)the recommanded way is to have a bundle of containers (
pod
s in kubernetes/rkt parlance), where user-containerA
requests resources or functionalities from containerB
(e.g. where thecvmfsd
daemon runs) this can be done either by sharingVOLUME
s (ie:cvmfsd
exposes/cvmfs
and containerA
mounts it) or via port remapping.we should refactor the
cvmfs-xyz
images to such a scheme.