Skip to content

Removed EOL Flocker plugin reference from plugin documentations. #6804

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
icemc wants to merge 2 commits into
base: master
Choose a base branch
from
+8 −9
Open

Removed EOL Flocker plugin reference from plugin documentations. #6804

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3aa4591
Removed EOL Flocker plugin reference from plugin documentations.
icemc Feb 16, 2026
345f223
docs: use generic myplugin example instead of VolumeDriver
icemc Mar 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions docs/extend/plugin_api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,12 +45,13 @@ spec files can be located either under `/etc/docker/plugins` or `/usr/lib/docker

The name of the file (excluding the extension) determines the plugin name.

For example, the `flocker` plugin might create a Unix socket at
`/run/docker/plugins/flocker.sock`.
For example, a plugin named `myplugin` might create a Unix socket at
`/run/docker/plugins/myplugin.sock`.

You can define each plugin into a separated subdirectory if you want to isolate definitions from each other.
For example, you can create the `flocker` socket under `/run/docker/plugins/flocker/flocker.sock` and only
mount `/run/docker/plugins/flocker` inside the `flocker` container.
For example, you can create the `myplugin` socket under `/run/docker/plugins/myplugin/myplugin.sock` and only
mount `/run/docker/plugins/myplugin` inside the `myplugin` container.


Docker always searches for Unix sockets in `/run/docker/plugins` first. It checks for spec or json files under
`/etc/docker/plugins` and `/usr/lib/docker/plugins` if the socket doesn't exist. The directory scan stops as
Expand Down
8 changes: 3 additions & 5 deletions docs/extend/plugins_volume.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ accepts a volume name and path on the host, and the `--volume-driver` flag
accepts a driver type.

```console
$ docker volume create --driver=flocker volumename
$ docker volume create --driver=myplugin volumename

$ docker container run -it --volume volumename:/data busybox sh
```
Expand All @@ -61,11 +61,9 @@ separated by a colon (`:`) character.
- The `Mountpoint` is the path on the host (v1) or in the plugin (v2) where the
volume has been made available.

### `volumedriver`
### `--volume-driver`

Specifying a `volumedriver` in conjunction with a `volumename` allows you to
use plugins such as [Flocker](https://github.com/ScatterHQ/flocker) to manage
volumes external to a single host, such as those on EBS.
Specifying a `VolumeDriver` in conjunction with a `VolumeName` allows you to use plugins to manage volumes.

## Create a VolumeDriver

Expand Down