vbatts/registry
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

- Pulling driver specs out of configuruation.md

Browse source 
- 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>
This commit is contained in:
Mary Anthony 2016-01-12 17:34:02 -08:00
parent 1df70eb1da
commit cab284d6b2
10 changed files with 651 additions and 495 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/storage-drivers/inmemory.md
View file

@ -7,11 +7,14 @@ keywords = ["registry, service, driver, images, storage, in-memory"]
<![end-metadata]-->
# In-memory storage driver
# In-memory storage driver (Testing Only)
An implementation of the `storagedriver.StorageDriver` interface which uses local memory for object storage.
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, and primarily exists for testing.
**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