Docker Engine Docker: Error response from daemon: storage driver not supported

The storage driver is not supported on the current system.

Understanding Docker Engine

Docker Engine is an open-source containerization technology that automates the deployment of applications as portable, self-sufficient containers that can run on the cloud or on-premises. It is a client-server application with a command-line interface (CLI) client, a REST API, and a server-side daemon process.

Identifying the Symptom

When using Docker, you might encounter the error message: Docker: Error response from daemon: storage driver not supported. This error indicates that the storage driver specified in your Docker configuration is not compatible with your current system setup.

Common Observations

  • Docker containers fail to start.
  • Error messages appear in the Docker logs.
  • Inability to perform Docker operations that rely on storage.

Details About the Issue

The error arises when Docker is configured to use a storage driver that is not supported by the host operating system. Storage drivers are crucial for managing how images and containers are stored on disk. Each driver has specific requirements and compatibility considerations.

Commonly Supported Storage Drivers

  • overlay2: Recommended for most Linux distributions.
  • aufs: Requires additional kernel modules and is less commonly used.
  • devicemapper: Often used in older systems but requires specific configuration.

Steps to Fix the Issue

To resolve the storage driver issue, follow these steps:

Step 1: Check Current Storage Driver

docker info | grep 'Storage Driver'

This command will show the current storage driver in use.

Step 2: Modify Docker Configuration

Edit the Docker daemon configuration file, typically located at /etc/docker/daemon.json. Add or modify the storage driver entry:

{
"storage-driver": "overlay2"
}

Ensure that the chosen storage driver is compatible with your system. For more information on storage drivers, visit the Docker Storage Driver documentation.

Step 3: Restart Docker Service

sudo systemctl restart docker

This command restarts the Docker service, applying the new configuration.

Conclusion

By following these steps, you should be able to resolve the storage driver issue and ensure that Docker operates smoothly on your system. For further reading, consider checking out the Docker CLI Reference and the Docker Engine Overview.

Never debug

Docker Engine

manually again

Let Dr. Droid create custom investigation plans for your infrastructure.

Book Demo
Automate Debugging for
Docker Engine
See how Dr. Droid creates investigation plans for your infrastructure.

MORE ISSUES

Made with ❤️ in Bangalore & San Francisco 🏢

Doctor Droid