• 2.5.5, 2.5 (jessie/2.5.5/Dockerfile)
• 2.7, 2.7.0, latest (jessie/2.7.0/Dockerfile)

For more information about this image and its history, please see the relevant manifest file (library/arangodb). This image is updated via pull requests to the docker-library/official-images GitHub repo.

For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see the arangodb/tag-details.md file in the docker-library/docs GitHub repo.

ArangoDB is a multi-model, open-source database with flexible data models for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions. Use ACID transactions if you require them. Scale horizontally and vertically with a few mouse clicks.

The supported data models can be mixed in queries and allow ArangoDB to be the aggregation point for the data request you have in mind.

arangodb.com

##Key Features in ArangoDB

Multi-Model Documents, graphs and key-value pairs — model your data as you see fit for your application.

Joins Conveniently join what belongs together for flexible ad-hoc querying, less data redundancy.

Transactions Easy application development keeping your data consistent and safe. No hassle in your client.

Joins and Transactions are key features for flexible, secure data designs, widely used in RDBMSs that you won't want to miss in NoSQL products. You decide how and when to use Joins and strong consistency guarantees, keeping all the power for scaling and performance as choice.

Furthermore, ArangoDB offers a microservice framework called Foxx to build your own Rest API with a few lines of code.

ArangoDB Documentation

• ArangoDB Documentation
• ArangoDB Tutorials

In order to start an ArangoDB instance run

$ docker run -d --name arangodb-instance arangodb

Will create and launch the arangodb docker instance as background process. The Identifier of the process is printed - the plain text name will be arangodb-instance as you stated above. By default ArangoDB listen on port 8529 for request and the image includes EXPOST 8529. If you link an application container it is automatically available in the linked container. See the following examples.

In order to get the IP arango listens on run:

$ docker inspect --format '{{ .NetworkSettings.IPAddress }}' arangodb-instance

In order to use the running instance from an application, link the container

$ docker run --name my-arangodb-app --link arangodb-instance:db-link arangodb

This will use the instance with the name arangodb-instance and link it into the application container. The application container will contain environment variables

DB_LINK_PORT_8529_TCP=tcp://172.17.0.17:8529
DB_LINK_PORT_8529_TCP_ADDR=172.17.0.17
DB_LINK_PORT_8529_TCP_PORT=8529
DB_LINK_PORT_8529_TCP_PROTO=tcp
DB_LINK_NAME=/naughty_ardinghelli/db-link

These can be used to access the database.

If you want to expose the port to the outside world, run

$ docker run -p 8529:8529 -d arangodb

ArangoDB listen on port 8529 for request and the image includes EXPOST 8529. The -p 8529:8529 exposes this port on the host.

ArangoDB use the volume /var/lib/arangodb as database directory to store the collection data and the volume /var/lib/arangodb-apps as apps directory to store any extensions. These directories are marked as docker volumes.

A good explanation about persistence and docker container can be found here: Docker In-depth: Volumes, Why Docker Data Containers are Good

You can map the container's volumes to a directory on the host, so that the data is kept between runs of the container. This path /tmp/arangodb is in general not the correct place to store you persistent files - it is just an example!

$ mkdir /tmp/arangodb
$ docker run -p 8529:8529 -d \
          -v /tmp/arangodb:/var/lib/arangodb \
          arangodb

This will use the /tmp/arangodb directory of the host as database directory for ArangoDB inside the container.

The ArangoDB startup configuration is specified in the file /etc/arangodb/arangodb.conf. If you want to use a customized ArangoDB configuration, you can create your alternative configuration file in a directory on the host machine and then mount that directory location as /etc/arangodb inside the arangodb container.

If /my/custom/arangod.conf is the path of your arangodb configuration file, you can start your arangodb container like this:

$ docker run --name some-arangodb -v /my/custom:/etc/arangodb -d arangodb:tag

This will start a new container some-arangodb where the ArangoDB instance uses the startup settings from your config file instead of the default one.

Note that users on host systems with SELinux enabled may see issues with this. The current workaround is to assign the relevant SELinux policy type to your new config file so that the container will be allowed to mount it:

$ chcon -Rt svirt_sandbox_file_t /my/custom

Alternatively you can create a container holding the data.

$ docker run -d --name arangodb-persist -v /var/lib/arangodb debian:8.0 true

And use this data container in your ArangoDB container.

$ docker run --volumes-from arangodb-persist -p 8529:8529 arangodb

If want to save a few bytes you can alternatively use hello-world, busybox or alpine for creating the volume only containers. For example:

$ docker run -d --name arangodb-persist -v /var/lib/arangodb alpine alpine

Arangodb itself is licensed under the Apache License, but it contains software of third parties under their respective licenses.

This image is officially supported on Docker version 1.9.0.

Support for older versions (down to 1.6) is provided on a best-effort basis.

Please see the Docker installation documentation for details on how to upgrade your Docker daemon.

Documentation for this image is stored in the arangodb/ directory of the docker-library/docs GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

If you have any problems with or questions about this image, please contact us through a GitHub issue.

You can also reach many of the official image maintainers via the #docker-library IRC channel on Freenode.

You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.