• Maintained by:
  Neo4j

• Where to get help:
  Neo4j Community Forums

• 5.11.0-community-bullseye, 5.11-community-bullseye, 5-community-bullseye, 5.11.0-community, 5.11-community, 5-community, 5.11.0-bullseye, 5.11-bullseye, 5-bullseye, 5.11.0, 5.11, 5, community-bullseye, community, bullseye, latest
• 5.11.0-enterprise-bullseye, 5.11-enterprise-bullseye, 5-enterprise-bullseye, 5.11.0-enterprise, 5.11-enterprise, 5-enterprise, enterprise-bullseye, enterprise
• 5.11.0-community-ubi8, 5.11-community-ubi8, 5-community-ubi8, 5.11.0-ubi8, 5.11-ubi8, 5-ubi8, community-ubi8, ubi8
• 5.11.0-enterprise-ubi8, 5.11-enterprise-ubi8, 5-enterprise-ubi8, enterprise-ubi8
• 4.4.24, 4.4.24-community, 4.4, 4.4-community
• 4.4.24-enterprise, 4.4-enterprise

• Where to file issues:
  https://github.com/neo4j/docker-neo4j/issues

• Supported architectures: (more info)
  amd64, arm64v8

• Published image artifact details:
  repo-info repo's repos/neo4j/ directory (history)
  (image metadata, transfer size, etc)

• Image updates:
  official-images repo's library/neo4j label
  official-images repo's library/neo4j file (history)

• Source of this description:
  docs repo's neo4j/ directory (history)

Neo4j is the world's leading graph database, with native graph storage and processing. 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.

For more examples and complete documentation please go to our manual here.

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 repo-info repository's neo4j/ directory.

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.