Error response from daemon: error looking up volume plugin "rexray": plugin not found
Fixes 'volume plugin not found' when using a third-party volume driver. Use when --volume-driver or compose driver_opts reference a plugin that is not installed. Not for local driver mount failures.
TL;DR: Install and enable the volume plugin first (docker plugin install rexray/ebs), then create the volume. The daemon cannot use a driver it does not have; the name in your volume or run command must match an installed, enabled plugin.
The error
Error response from daemon: error looking up volume plugin "rexray": plugin not foundFix it
- List installed plugins:
docker plugin ls Expected: the driver missing or DISABLED.
- Install it:
docker plugin install rexray/ebs --grant-all-permissions Expected: installs and enables.
- If present but disabled:
docker plugin enable rexray/ebs
- Retry the volume create / container run.
When this applies
- Cloud volume drivers (rexray, portworx), NFS or Ceph plugins referenced but not installed
- Compose files with
driver: rexraymoved between hosts
When this does NOT apply
- Local driver volumes (built in, never "not found")
- Plugin installed but failing at runtime (check
docker plugin inspectand plugin logs)
Versions
Docker Engine 17.06+ (managed plugin system).
Why it happens
Volume drivers are separate plugin processes. The name is just a string until the daemon resolves it against installed plugins; a typo or a fresh host without the install step fails lookup.
Edge cases
- Plugins need
--grant-all-permissionsat install or they sit disabled awaiting approval. - Plugin names include the repo:
docker plugin install vieux/sshfsthen reference drivervieux/sshfs. - After daemon upgrade, plugins sometimes stay disabled; re-enable them.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.