• 3.0.6, 3.0, latest (3.0.6/community/Dockerfile)
• 3.0.6-enterprise, 3.0-enterprise, enterprise (3.0.6/enterprise/Dockerfile)
• 3.0.5 (3.0.5/community/Dockerfile)
• 3.0.5-enterprise (3.0.5/enterprise/Dockerfile)
• 3.0.4 (3.0.4/community/Dockerfile)
• 3.0.4-enterprise (3.0.4/enterprise/Dockerfile)
• 3.0.3 (3.0.3/community/Dockerfile)
• 3.0.3-enterprise (3.0.3/enterprise/Dockerfile)
• 3.0.2 (3.0.2/community/Dockerfile)
• 3.0.2-enterprise (3.0.2/enterprise/Dockerfile)
• 3.0.1 (3.0.1/community/Dockerfile)
• 3.0.1-enterprise (3.0.1/enterprise/Dockerfile)
• 3.0.0 (3.0.0/community/Dockerfile)
• 3.0.0-enterprise (3.0.0/enterprise/Dockerfile)
• 2.3.6, 2.3 (2.3.6/community/Dockerfile)
• 2.3.6-enterprise, 2.3-enterprise (2.3.6/enterprise/Dockerfile)
• 2.3.5 (2.3.5/community/Dockerfile)
• 2.3.5-enterprise (2.3.5/enterprise/Dockerfile)
• 2.3.4 (2.3.4/community/Dockerfile)
• 2.3.4-enterprise (2.3.4/enterprise/Dockerfile)
• 2.3.3 (2.3.3/community/Dockerfile)
• 2.3.3-enterprise (2.3.3/enterprise/Dockerfile)
• 2.3.2 (2.3.2/community/Dockerfile)
• 2.3.2-enterprise (2.3.2/enterprise/Dockerfile)
• 2.3.1 (2.3.1/community/Dockerfile)
• 2.3.1-enterprise (2.3.1/enterprise/Dockerfile)
• 2.3.0 (2.3.0/community/Dockerfile)
• 2.3.0-enterprise (2.3.0/enterprise/Dockerfile)

For more information about this image and its history, please see the relevant manifest file (library/neo4j). 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 repos/neo4j/tag-details.md file in the docker-library/repo-info GitHub repo.

Neo4j is a highly scalable, robust, native graph database. It is used in mission-critical apps by thousands of leading startups, enterprises, and governments around the world. You can learn more here.

You can start a Neo4j container like this:

docker run \
    --publish=7474:7474 --publish=7687:7687 \
    --volume=$HOME/neo4j/data:/data \
    neo4j

which allows you to access neo4j through your browser at http://localhost:7474.

This binds two ports (7474 and 7687) for HTTP and Bolt access to the Neo4j API. A volume is bound to /data to allow the database to be persisted outside the container.

By default, this requires you to login with neo4j/neo4j and change the password. You can, for development purposes, disable authentication by passing --env=NEO4J_AUTH=none to docker run.

Neo4j 3.0 introduced several major user-facing changes, primarily the new binary Bolt protocol. This is not available in 2.3 and as such, there is no need to expose the 7687 port. Due to changes made to the structure of configuration files, several environment variables used to configure the image has changed as well. Please see the 2.x specific section in the manual for further details.

You can start an instance of Neo4j 2.3 like this:

docker run \
    --publish=7474:7474 \
    --volume=$HOME/neo4j/data:/data \
    neo4j:2.3

For more examples and complete documentation please go here for 2.x and here for 3.x.

This image is officially supported on Docker version 1.12.3.

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.

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

For general Neo4j questions, please ask on StackOverflow.

We welcome pull requests on GitHub.