Good morning, Dave, Amongst reasons for not running Docker, a major one that I didn't notice > raised is that containers are not started by the resource manager, but > by a privileged daemon, so the resource manager can't directly control > or monitor them. >
There's an endless debate <https://lwn.net/Articles/676831/> about this between the docker and systemd folks. It is possible to get at the underlying process <https://github.com/docker/docker/issues/6791> if a resource manager wanted to. > From a brief look at Jupyter when it came up a while ago, I wouldn't > want to run it, and I wasn't alone. (I've been lectured about the lack > of problems with such things by people on whose clusters I could > trivially run jobs as any normal user and sometimes as root.) > Well some people disagree, e.g. ipython.nersc.gov. Our users like Jupyter. It's my job to help them use it. +1 for what Ralph said about singularity in particular. While there's > work to be done, you could even convert docker images on the fly in a > resource manager prolog. I'm awaiting enlightenment on the on-topic > issue of running MPI jobs with it, though. > > I don't see how Singularity addresses the problem of starting MPI inside Docker. In any event, our current plan is to bypass resource managers completely and start an AWS fleet per user request. The code is much simpler for everybody. Rob
