Official Docker images for running Neo4j graph database in containers.
docker-neo4j is the official repository for Docker images of the Neo4j graph database. It provides pre-built container images that allow developers to run Neo4j instances quickly and consistently in Docker environments. The project simplifies deployment by packaging Neo4j with its dependencies and configurations ready for containerized use.
Developers and DevOps engineers who need to deploy Neo4j graph databases in containerized environments, whether for local development, testing, or production deployments using Docker.
It offers officially maintained, production-ready Docker images that ensure compatibility with Neo4j releases, include both Community and Enterprise editions, and support persistent data storage and multi-architecture deployments.
Docker Images for the Neo4j Graph Database
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Images are officially maintained and hosted on Docker Hub, ensuring compatibility with Neo4j releases and recommended for production use, as stated in the README.
Supports volume mounting for /data and /logs directories, allowing data to persist across container restarts, demonstrated in the example Docker run commands.
Includes ARM64 images from version 4.4.0 onwards, making it compatible with modern hardware like Apple Silicon and Raspberry Pi, as highlighted in the README.
Simple Docker run commands with default ports (7474 and 7687) enable rapid instance spinning without complex configuration, shown in the provided examples.
ARM64 images for versions before 4.4.0 are experimental and unsupported, posing risks for production use on older ARM systems, as admitted in the README.
Detailed usage instructions are linked to external Neo4j documentation, which can be fragmented and less convenient than having integrated docs in the repository.
Some Neo4j features, such as advanced clustering or performance tuning, might be more challenging to configure in Docker compared to native installations, requiring extra orchestration effort.