SwarmSpawner does not allow configuration for container placement

isuftin commented 7 years ago

When running JupyterHub on Docker Swarm using the SwarmSpawner, JupyterHub has no way to dictate where the new Docker container for a user's notebook will appear. This allows notebooks to run on manager nodes as well as worker nodes. This causes several issues:

Managers should not have notebook containers running on them
Indeterminate placement causes a user's backing Docker volume to maybe not be available to them if the Docker container is started on a new worker or manager than that which previously ran the notebook

isuftin commented 7 years ago

Waiting for SwarmSpawner author to merge PR https://github.com/cassinyio/SwarmSpawner/pull/19 which allows placement of containers to specific nodes.

isuftin commented 7 years ago

In the meantime, using my own fork of the project to get that functionality into the image. Is working as expected

USGS-CMG / data-life-cycle-cloud-docker-jupyterhub

SwarmSpawner does not allow configuration for container placement #8