
armel/neo4jThe armel organization is deprecated in favor of the more-specific arm32v5 organization, as per [***] Please adjust your usages accordingly.
Dockerfile links** THESE IMAGES ARE VERY EXPERIMENTAL; THEY ARE PROVIDED ON A BEST-EFFORT BASIS WHILE docker-library/official-images#2289 IS STILL IN-PROGRESS (which is the first step towards proper multiarch images) **
** PLEASE DO NOT USE THEM FOR IMPORTANT THINGS **
This image is built from the source of the official image of the same name (neo4j). Please see that image's description for links to the relevant Dockerfiles.
If you are curious about specifically how this image differs, see the Jenkins Groovy DSL scripts in the tianon/jenkins-groovy GitHub repository, which are responsible for creating the Jenkins jobs which build them.
Where to get help:
Stack Overflow
Where to file issues:
[***]
Maintained by:
Neo4j
Published image artifact details:
repo-info repo's repos/neo4j/ directory (history)
(image metadata, transfer size, etc)
Image updates:
official-images PRs with label library/neo4j
official-images repo's library/neo4j file (history)
Source of this description:
docs repo's neo4j/ directory (history)
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
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.
!logo
You can start a Neo4j container like this:
consoledocker 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:
consoledocker 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.


manifest unknown 错误
TLS 证书验证失败
DNS 解析超时
410 错误:版本过低
402 错误:流量耗尽
身份认证失败错误
429 限流错误
凭证保存错误
来自真实用户的反馈,见证轩辕镜像的优质服务