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.

  • Using a dedicated proxy container in front of Rails app container
  • docker swarm init on windows container output nothing
  • Make container accessible only from localhost
  • Docker-compose: resolving mongo container from Angular client code
  • Using Docker file sharing but file does not seem to be updating
  • How is load balancing done in Docker-Swarm mode
  • 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?

  • docker on windows not working
  • gcloud docker pull fails with Untar exit status 2 unexpected fault address
  • docker website opens after a while - ec2/virtualbox
  • Does my proxied server need to use HTTPS protocol with docker linking?
  • Handling cron jobs in docker?
  • Running a single Docker Cloud's HAProxy container with SSL and non-SSL simultaneously
  • 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.