You can create a user inside a docker machine just like any other and
then just ssh to it. We run openmpi jobs with some ranks on physical
hardware and some inside docker.
On 05/19/2015 10:14 AM, Kilian Cavalotti wrote:
On Tue, May 19, 2015 at 9:28 AM, Michael Jennings <[email protected]> wrote:
What Chris is asking for, I *think*, is what we're looking for as well --
anyone who has figured out a way to allow users to execute jobs inside
user-supplied (or at least user-specified) Docker containers. It would be nice
to be able to allow users to supply not only the data, scripts, and programs
that compose their job but also the OS environment (in the form of a Docker
container or Dockerfile) within which it should execute.
One major downside to running Docker containers in a shared HPC
cluster (to me at least), is that the default user in a container is
root. And that it can easily map and access the host filesystem from
inside the container. Letting users run as root on a shared cluster is
a major no-go from my perspective. So until Docker folks figure out a
way to avoid this (and work on this seems to have just started very
recently: https://github.com/docker/docker/issues/12949), I don't see
much appeal from running Docker containers on a shared HPC cluster.
There may be other use cases, of course.
But if users running as root is not an issue, what more is needed from
Slurm to launch containers? I may very well be missing something, but
If you have a docker daemon running on all of your compute nodes, and
provided users can access the docker socket/port, they can submit jobs
that call "docker run", can't they?
Cheers,
--
Thanks,
/David/Bigagli
www.schedmd.com
