Docker Compose "volume driver not found" in CI

By Daniel Zoghalchali·Latchkey

A named volume with a custom driver: requires that volume plugin to be installed on the host. When the plugin is absent - a host without the NFS/cloud/CSI plugin the compose file expects - creating the volume fails with volume plugin not found.

What this error means

A docker compose up fails creating a volume with error looking up volume plugin <driver>: plugin not found. The compose file requests a driver the host lacks.

Error response from daemon: create app-data: error looking up volume plugin rexray/efs: plugin not found

Common causes

The volume plugin is not installed

A custom driver: references a plugin the host does not have installed/enabled.

A plugin available on dev but not on the runner

The compose file assumes a plugin present locally but missing on the CI host.

How to fix it

Install the volume plugin on the host

1. Install/enable the required plugin, then bring up compose.

docker plugin install rexray/efs
docker plugin ls
docker compose up -d

Use the local driver for CI

1. Override the volume to use the built-in local driver where the plugin is unavailable.

volumes:
  app-data:
    driver: local

How to prevent it

• Install required volume plugins on every runner host.
• Override custom drivers to local in CI when appropriate.
• Keep compose volume drivers consistent across environments.

Frequently asked questions

Related guides

References

• Docker documentation
• Docker build cache
• GitHub Actions documentation