Personal tools
Skip to content. | Skip to navigation
When a volume in provisioned via the `VOLUME` instruction in a Dockerfile or via `docker run -v volumename`, host's storage space is used. This could lead to an unexpected out of space issue which could bring down everything. There are situations where this is not an accepted behavior. PAAS, for instance, can't allow their users to run their own images without the risk of filling the entire storage space on a server. One solution to this is to deny users from running images with volumes. This way the only storage a user gets can be limited and PAAS can assign quota to it. This plugin solves this issue by disallowing starting a container with local volumes defined. In particular, the plugin will block `docker run` with: - `--volumes-from` - images that have `VOLUME`(s) defined - volumes early provisioned with `docker volume` command The only thing allowed will be just bind mounts.
Registry server for Docker (hosting/delivering of repositories and images).
SELinux policy modules for use with Docker.
Docker Swarm is native clustering for Docker. It turns a pool of Docker hosts into a single, virtual host. Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Flynn, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself. Like other Docker projects, Swarm follows the "batteries included but removable" principle. It ships with a set of simple scheduling backends out of the box, and as initial development settles, an API will be developed to enable pluggable backends. The goal is to provide a smooth out-of-the-box experience for simple use cases, and allow swapping in more powerful backends, like Mesos, for large scale production deployments.
External utilities for the docker experience