Docker ERROR: Volume specifies nonexistent driver inmemory

According to the docs there is a ‘inmemory’ driver for docker volumes:

For purely tests purposes, you can use the inmemory storage driver.
This driver is an implementation of the storagedriver.StorageDriver
interface which uses local memory for object storage.

  • How to notify application about updated config file in kubernetes?
  • Service running in Docker returning URLs to another service service in different container
  • Docker php:5.6-apache 403 (because search permissions are missing on a component of the path)
  • Flask API breaks at long Cypher query
  • How to read environment variables during a docker image build process?
  • Linking Docker container : Node.js + MongoDB
  • But when trying to use it like so:

        driver: inmemory

    It gives me this output:

    Creating volume "myapp_ui-tmp-memory" with inmemory driver
    ERROR: Volume ui-tmp-memory specifies nonexistent driver inmemory

    Am I missing something or do I need to install “inmemory” driver somehow?

  • Is it possible to mount one Path to all container by default?
  • Ambiguous port publish parameters to “docker run”
  • Celery not finding a Python module in it's working directory
  • Container with app + DB
  • smtp sendmail in Dockerised Golang Web App in GAE doesn't work
  • Docker service does not start
  • One Solution collect form web for “Docker ERROR: Volume specifies nonexistent driver inmemory”

    The link you’ve provided points to storage drivers for Docker Registry. You seem to want to mount a volume in a container which would require a Docker Engine Volume Plugin. These are two distinct types of plugins for two different applications and aren’t interchangeable.

    You may be able to easily accomplish what you want by creating a RAM disk and using the Local Persist Plugin in Docker Engine.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.