docker-novolume-plugin - Block container starts with local volumes defined
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.
|docker-novolume-plugin-1.12.6-13.gitf499e8b.el7.centos.x86_64 [1.9 MiB]||
by Sandeep Sangamreddi (2017-01-14):
- built docker @projectatomic/docker-1.12 commit f499e8b - built docker-selinux commit - built d-s-s commit f7a3746 - built docker-novolume-plugin commit c521254 - built docker-runc @projectatomic/runc-1.12 commit 81b2542 - built docker-utils commit - built docker-containerd commit 471f03c - built docker-v1.10-migrator commit 994c35c