Docker issue on large maps

Hello,

First, I would like to thank for your really great open-source software.
Second, I do not know if I should post here or on the github as it’s a technical problem.
I’ve tried to run the dockerfile and I have some issues to connect to the localhost.
When I run the dockerfile on a small map, I do not have any problem to connect and query my local server, but I soon as I use a bigger map (let’s say the midwest for the us), I am not anymore able to connect to the localhost. I’ve tried to change the java options as well as to export JETTY_PORT and GH_FOREGROUND, and it’s still not working. I’ve seen that GH_FOREGROUND=“false” doesn’t work for a small map also.

I can send the Dockerfile and docker-compose that I’m using if necessary (but I cannot for the moment as I’m a new user).

Thanks,

Here my current log:

Attaching to disp-graph-hopper
disp-graph-hopper | ## using java (64bit) from /docker-java-home
disp-graph-hopper | ./graphhopper.sh: line 86: mvn: command not found
disp-graph-hopper | ## using existing osm file /data/us-midwest-latest.osm.pbf
disp-graph-hopper | ## existing jar found tools/target/graphhopper-tools-0.9-SNAPSHOT-jar-with-dependencies.jar
disp-graph-hopper | ## now web. JAVA_OPTS=-server -Xconcurrentio -Xmx10g -Xms10g -XX:+UseG1GC -XX:MetaspaceSize=100M
disp-graph-hopper | 2017-05-22 21:19:22,568 [main] INFO com.graphhopper.http.CmdArgsModule - jsonp disabled
disp-graph-hopper | 2017-05-22 21:19:23,170 [main] INFO com.graphhopper.http.GraphHopperModule$1 - version 0.9|2017-05-22T19:00:11Z (5,14,4,3,3,2)
disp-graph-hopper | 2017-05-22 21:19:23,177 [main] INFO com.graphhopper.http.GraphHopperModule$1 - graph CH|car|RAM_STORE|2D|NoExt|, details:edges:0(0MB), nodes:0(0MB), name:(0MB), geo:0(0MB), bounds:1.7976931348623157E308,-1.7976931348623157E308,1.7976931348623157E308,-1.7976931348623157E308, CHGraph|fastest|car, shortcuts:0, nodesCH:(0MB)
disp-graph-hopper | 2017-05-22 21:19:23,184 [main] INFO com.graphhopper.http.GraphHopperModule$1 - start creating graph from /data/us-midwest-latest.osm.pbf
disp-graph-hopper | 2017-05-22 21:19:23,184 [main] INFO com.graphhopper.http.GraphHopperModule$1 - using CH|car|RAM_STORE|2D|NoExt|, memory:totalMB:10240, usedMB:53

Did you wait a bit to complete the import? (The waiting time can be hours for large areas)

I’ve seen that GH_FOREGROUND=“false” doesn’t work for a small map also.

A pull request would be welcome :slight_smile:

You’re right, I can see it’s taking a lot of time …
A pull request ? I can push my docker-compose file and Dockerfile if you wish.

Thank you very much

You’re right, I can see it’s taking a lot of time …

It is a one time thing… when you restart it should be up in <1min

I mean a contribution where you improve our current dockerfile or graphhopper.sh script so that it works like you would have expected

Hi,

I’ve send a pull request with the docker-compose file and some others modifications.
I’m also trying to use the geocoding part, and I’ve receive a response message not found. Do I need to install photon or I can use it directly from graphhopper ?

thanks

1 Like

Geocoding is not part of the routing engine and you can use external services or install it locally

Ok thank you. Just a remark: on your website, it’s seems that the Geocoding part is available on the opensource repo: https://www.graphhopper.com/open-source/

There are many open source projects that we push out or support. One of them is the routing engine where geocoding is not part of.

Thank you. Sorry for the misunderstanding. For geocoding, I may use photon.