Apache HugeGraph DockerHub: https://hub.docker.com/r/hugegraph/hugegraph

Usage:

# 0. download image (latest) docker pull hugegraph/hugegraph # 1. start container docker run -itd hugegraph/hugegraph # start server in daemon mode # (Optional configs to expose network port outside) docker run -itd --name=graph -p 18080:8080 hugegraph/hugegraph # 2. (Optional) enter the container & start hugegraph-hubble docker exec -it graph bash xxx 

Feature Needs

1. Add Dockerfile for running HugeServer
2. Users can pull/run the image from dockerhub directly.

And anyone who has other suggestion for docker image can comment here

After PR, will update the doc 📝

Update in 2023.11.09:

Due to the project will move to Apache Foundation, we'll use 1.0.0 as the server version & bind hubble with it, reopen this issue until it meets the new need, any suggestions for Dockerfile are welcome.

• Dockerfile start cmd & restart problem [Question] Dockerfile misc problems #2343
• use docker-slim to slim the image
• use docker-compose to manage computer, it needs to contain etcd and hugegraph-server
• use DockerHub(autobuild), currently it's not free to use (Submit a OSS request)
• fix that hubble can't use localhost/0.0.0.0 & add a script to update the image
• use a script to run server & hubble together OR use docker-compose to manage them
• support Cassandra(Docker) as backend (compose with HugeGraph) feat: support Cassandra with docker-compose in server #2307
• keep the tags same with server (like hugegraph/hugegraph:1.0.0) feat: support publish_server_image to dockerhub automatically (V2) hugegraph/actions#1
• pre-load some data or graphs in container so that users can traverse the graph with one step feat(dist): support pre-load test graph data in docker container #2241
• use hubble instead of studio to support new features
• support ARM env (for M1 laptop, refer doc)
• consider better way (like add a option/program to run backward) to avoid modify start-script refact: use a slim way to build docker image on latest code & support zgc #2118
• adopt v0.12 (support raft based replication)
• use github actions to publish images
• use jdk11 for runtime refact: use a slim way to build docker image on latest code & support zgc #2118
• use multi-stage Dockerfile way to slim the image
• support build from the (latest) source code refact: use a slim way to build docker image on latest code & support zgc #2118

Refer:

1. Reduce the size of container images with DockerSlim
2. One docker container with multi process (Not graceful:)
3. How to use dumb-init to replace the pid1 in docker