janusgraph-docker icon indicating copy to clipboard operation
janusgraph-docker copied to clipboard

ARM64 Image

Open dantestopp opened this issue 4 years ago • 2 comments

I would like to run a development environment with Janusgraph, Solr and Cassandra on my Raspberry Pies. Solr and Cassandra both provide ARM64 compatible images on Docker Hub.

Sadly Janusgraph only provides AMD images.

It would be nice if Janusgraph had also compatible images.

Thank you for your feedback.

dantestopp avatar Oct 04 '21 13:10 dantestopp

Supporting ARM64 sounds like a good idea of course and there seems to be a lot of interest in this, considering the amount of 👍 this already got. Anyone here who is willing to provide a PR for this?

FlorianHockmann avatar Jun 16 '22 10:06 FlorianHockmann

@FlorianHockmann this should be prioritised

analytically avatar Oct 04 '22 20:10 analytically

Any updates on this? I noticed 1.0RC came out but still no ARM support.

Jrb1x avatar Dec 20 '22 21:12 Jrb1x

I have made a PR. I also uploaded the images to my personal docker-hub: https://hub.docker.com/r/liboxuanhk/janusgraph/tags

li-boxuan avatar Jan 03 '23 05:01 li-boxuan

Note that the ./bin/gremlin.sh inside the Docker image won't work for ARM machines due to the following error:

Exception in thread "main" java.lang.UnsatisfiedLinkError: Could not load library. Reasons: [no jansi in java.library.path, /tmp/libjansi-64-8999118035290383984.so: /tmp/libjansi-64-8999118035290383984.so: cannot open shared object file: No such file or directory (Possible cause: can't load AMD 64-bit .so on a AARCH64-bit platform)]

I am not sure why this is the case but running the server alone inside the Docker image is fine. I am able to download the zip file from https://github.com/JanusGraph/janusgraph/releases and use the local gremlin console to connect to the server (running in Docker). I am using openjdk version "1.8.0_275".

Seems the error message comes from a dependency of TinkerPop: https://github.com/fusesource/jansi/issues/207 but somehow it only fails to work in the Docker environment. Maybe it's due to the base environment that the Docker image uses.

li-boxuan avatar Jan 05 '23 04:01 li-boxuan