Supported tags and respective
No supported tags found!
It is very likely that
neo4j does not support the currently selected architecture (
Where to get help:
Where to file issues:
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What is Neo4j?
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.
How to use this image
Start an instance of neo4j
You can start a Neo4j container like this:
docker run \ --publish=7474:7474 --publish=7687:7687 \ --volume=$HOME/neo4j/data:/data \ ppc64le/neo4j
which allows you to access neo4j through your browser at http://localhost:7474.
This binds two ports (
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.
Note on version 2.3
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 \ ppc64le/neo4j:2.3
View licensing information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.