如何运行Hetionet v1.0 docker容器？

本文介绍了如何运行Hetionet v1.0 docker容器？的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我试图运行

现在我运行 docker run dhimmel / hetionet 并发生以下情况（并且不会返回到交互式shell提示符）。

如果成功完成，应该做的是运行 sh〜/ run-docker.sh 。此外，我的水滴的ip_address还没有活着：7474。

上面截图中的错误看起来很像它可能与一些冗余的 @Path（/）注释，如这个SO帖子的评论所述，埋在码头容器中，但我不确定。 p>

运行 docker的输出运行dhimmel / hetionet 应该挂起我的shell吗？我在Ubuntu 16.04上使用Docker 1.12.5运行2 GB内存/ 40 GB磁盘滴。

解决方案

感谢您的对 Hetionet Docker 的兴趣。

预期输出为3。看起来Docker容器成功启动，下载了Hetionet数据库，并启动了Neo4j服务器。我将研究修复警告，但它们不是错误，如Neo4j仍然启动。

对于生产，我们使用更高级的Docker 运行命令。根据您的用例，您可能需要使用开发码头工具运行命令：

docker run \ - 发布= 7474：7474 \ --publish = 7687：7687 \ --volume = $ HOME / neo4j / hetionet-data：/ data \ --volume = $ HOME / neo4j / hetionet-logs：/ var / lib / neo4j / logs \ dhimmel / hetionet

生产和开发命令都映射端口。这样做将使您的Docker容器中运行的Neo4j服务器可以在 http：// localhost：7474 / 上获取。这很可能是你想要的。如果您在DigitalOcean上执行此操作，您将用液滴的IP地址替换 http：// localhost 。

对于 dhimmel / hetionet 容器中的交互式shell会话，您可以使用：

docker run --interactive --tty dhimmel / hetionet bash

然而，命令不启动Neo4j服务器 - 它只是让您探索​​图像。

这是否清楚了？

I'm trying to run the Hetionet v1.0 docker container mentioned in this SO post.

I've setup a digitalocean droplet with Docker

I ran docker pull dhimmel/hetionet and it worked

Now I run docker run dhimmel/hetionet and the following happens (and never returns to the interactive shell prompt).

If that completed successfully I think the last thing I'm supposed to do is run sh ~/run-docker.sh. Furthermore nothing is live at my droplet's ip_address:7474.

The error in the screenshot above looks a lot like it could be related to some redundant @Path("/") annotation, as described in this SO post's comment, buried in the docker container but I'm not sure.

Is the output from running docker run dhimmel/hetionet supposed to hang my shell? I'm running a 2 GB Memory / 40 GB Disk Droplet on Ubuntu 16.04 with Docker 1.12.5.

解决方案

Thanks for your interest in the Hetionet Docker.

The output in 3 is expected. It looks like a Docker container successfully launched, downloaded the Hetionet database, and launched the Neo4j server. I'll look into fixing the warnings, but they're not errors, as Neo4j is still launching.

For production, we use a more advanced Docker run command. Depending on your use case, you may want to use the development docker run command:

docker run \ --publish=7474:7474 \ --publish=7687:7687 \ --volume=$HOME/neo4j/hetionet-data:/data \ --volume=$HOME/neo4j/hetionet-logs:/var/lib/neo4j/logs \ dhimmel/hetionet

Both the production and development command map ports. This will make it so the Neo4j server running inside your Docker container is available at localhost:7474/. This is most likely what you want. If you're doing this on DigitalOcean, you would replace localhost with the IP address of your droplet.

For an interactive shell session in a dhimmel/hetionet container, you can use:

docker run --interactive --tty dhimmel/hetionet bash

However, that command does not launch the Neo4j server -- it just let's you explore the image.

Does this clear things up?