registry/docs/storage-drivers/inmemory.md

<!--[metadata]>
+++
title = "In-memory storage driver"
description = "Explains how to use the in-memory storage drivers"
keywords = ["registry, service, driver, images, storage,  in-memory"]
+++
<![end-metadata]-->


# In-memory storage driver (Testing Only)

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. If you would like to run a registry from
volatile memory, use the [`filesystem` driver](filesystem.md) on a ramdisk.

**IMPORTANT**: This storage driver *does not* persist data across runs. This is why it is only suitable for testing. *Never* use this driver in production.

## Parameters

None
Updating for Hugo Updating for tooling tests Updating with the new sed scripts to protect links updating with new image Updating with comments Signed-off-by: Mary Anthony <mary@docker.com> 2015-06-08 00:58:53 +00:00			`<!--[metadata]>`
			`+++`
			`title = "In-memory storage driver"`
			`description = "Explains how to use the in-memory storage drivers"`
			`keywords = ["registry, service, driver, images, storage, in-memory"]`
			`+++`
			`<![end-metadata]-->`

Fixes Issue #471 with Publish - Add sed to Dockerfile; this sed exists on publish script; breaks headings/nav in files without metadata - Ensure sed runs over storage-driver/ subdir - Add metadata to all the files (including specs) that don't have it; this ensures they display correctly on publish - Implement the fix for the showing up in Github - Update template with GITHUB IGNORES Signed-off-by: Mary Anthony <mary@docker.com> 2015-04-29 19:20:09 +00:00
- Pulling driver specs out of configuruation.md - Fixing index metadata error - Entering all the comments - Updating with the build fixes - Fix Microsoft link broken - Fix collocate, colocate, to unambiguous co-locate Signed-off-by: Mary Anthony <mary@docker.com> 2016-01-13 01:34:02 +00:00			`# In-memory storage driver (Testing Only)`
Adds basic READMEs to inmemory and filesystem storage drivers 2014-12-29 21:59:40 +00:00
- Pulling driver specs out of configuruation.md - Fixing index metadata error - Entering all the comments - Updating with the build fixes - Fix Microsoft link broken - Fix collocate, colocate, to unambiguous co-locate Signed-off-by: Mary Anthony <mary@docker.com> 2016-01-13 01:34:02 +00:00			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. If you would like to run a registry from`
			volatile memory, use the [`filesystem` driver](filesystem.md) on a ramdisk.
Adds basic READMEs to inmemory and filesystem storage drivers 2014-12-29 21:59:40 +00:00
- Pulling driver specs out of configuruation.md - Fixing index metadata error - Entering all the comments - Updating with the build fixes - Fix Microsoft link broken - Fix collocate, colocate, to unambiguous co-locate Signed-off-by: Mary Anthony <mary@docker.com> 2016-01-13 01:34:02 +00:00			`IMPORTANT: This storage driver does not persist data across runs. This is why it is only suitable for testing. Never use this driver in production.`
Adds basic READMEs to inmemory and filesystem storage drivers 2014-12-29 21:59:40 +00:00
			`## Parameters`

			`None`