From cf7e2c15afdf853b1ae956ece2038a1d3564d263 Mon Sep 17 00:00:00 2001 From: Simran Date: Wed, 26 Aug 2020 13:23:00 +0200 Subject: [PATCH] Remove 2.x content --- arangodb/content.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/arangodb/content.md b/arangodb/content.md index 980c89081..935d90487 100644 --- a/arangodb/content.md +++ b/arangodb/content.md @@ -153,9 +153,7 @@ See more information about [Configuration](https://www.arangodb.com/docs/stable/ ArangoDB supports two different storage engines from version 3.2 to 3.6. You can choose them while instantiating the container with the environment variable `ARANGO_STORAGE_ENGINE`. With `mmfiles` you choose the classic storage engine (not available in 3.7 and later), `rocksdb` will choose the storage engine based on [RocksDB](http://rocksdb.org/). The default choice is `rocksdb` from version 3.4 on. -ArangoDB use the volume `/var/lib/arangodb3` as database directory to store the collection data and the volume `/var/lib/arangodb3-apps` as apps directory to store any extensions. These directories are marked as docker volumes. - -Please note that the old version 2.x used `/var/lib/arangodb` and `/var/lib/arangodb-apps`. We will refer to the 3.x variant in this document. In case you are starting a 2.x image just replace it with the 2.x variant. +ArangoDB uses the volume `/var/lib/arangodb3` as database directory to store the collection data and the volume `/var/lib/arangodb3-apps` as apps directory to store any extensions. These directories are marked as docker volumes. See `docker inspect --format "{{ .Config.Volumes}}" arangodb` for all volumes.