A fork of GIS-OPS Valhalla Docker image, for better integration with Pelias
282
A hyper-flexible Docker image for the excellent Valhalla routing framework.
docker run -dt --name valhalla_gis-ops -p 8002:8002 -v $PWD/custom_files:/custom_files gisops/valhalla:latest
This image aims at being user-friendly and most efficient with your time and resources. Once built, you can easily change Valhalla's configuration, the underlying OSM data graphs are built from, accompanying data (like Admin Areas, elevation tiles) or even pre-built graph tiles. Upon docker restart <container> those changes are taken into account via hashed files, and, if necessary, new graph tiles will be built automatically.
In the Dockerhub repository you'll find the following images/tags:
latest, updated from Valhalla Github repository every Saturday morningIf you want to build the image yourself, be aware that you might need to adapt the base image in the Dockerfile to reflect the version of Valhalla you'd like to build. You can find the tags of the valhalla/valhalla:run-* images here: https://hub.docker.com/r/valhalla/valhalla/tags.
Note, that this is only valid down to 3.1.0, before the building scheme was completely different. Please contact [email protected] if you need access to previous Valhalla versions via Docker.
Then it's a simple
docker build -t gisops/valhalla .
This image respects the following custom environment variables to be passed during container startup. Note, all variables have a default:
tile_urls: Add as many (space-separated) URLs as you like, e.g. https://download.geofabrik.de/europe/andorra-latest.osm.pbf http://download.geofabrik.de/europe/faroe-islands-latest.osm.pbf. Default "".min_x: Minimum longitude for elevation tiles, in decimal WGS84, e.g. 18.5min_y: Minimum latitude for elevation tiles, in decimal WGS84, e.g. 18.5max_x: Maximum longitude for elevation tiles, in decimal WGS84, e.g. 18.5max_y: Maximum latitude for elevation tiles, in decimal WGS84, e.g. 18.5use_tiles_ignore_pbf: True uses a local tile.tar file and skips building. Default False.force_rebuild: True forces a rebuild of the routing tiles. Default False.build_elevation: True builds elevation for the set coordinates. Force will do the same, but first delete any existing elevation tiles. Default False.build_admins: True builds the admin db. Force will do the same, but first delete the existing db. Default False.build_time_zones: True builds the timezone db. Force will do the same, but first delete the existing db. Default False.server_threads: How many threads valhalla_service will run with. Default is 1 thread less than the value of nproc.For the following instructions to work, you'll need to have the image locally available already, either from Docker Hub or from local.
Start a background container from that image:
docker run -dt -v $PWD/custom_files:/custom_files -p 8002:8002 --name valhalla gisops/valhalla:latest
The important part here is, that you map a volume from your host machine to the container's /custom_files. The container will dump all relevant Valhalla files to that directory.
At this point Valhalla is running, but there is no graph tiles yet. Follow the steps below to customize your Valhalla instance in a heartbeat.
Note, alternatively you could create
custom_fileson your host before starting the container with all necessary files you want to be respected, e.g. the OSM PBF files.
Just dump single or multiple OSM PBF files to your mapped custom_files directory, restart the container and Valhalla will start building the graphs:
cd custom_files
# Download Andorra & Faroe Islands
wget http://download.geofabrik.de/europe/faroe-islands-latest.osm.pbf http://download.geofabrik.de/europe/andorra-latest.osm.pbf
docker restart valhalla
If you change the PBF files by either adding new ones or deleting any, Valhalla will build new tiles on the next restart unless told not to (e.g. setting use_tiles_ignore_pbf=True).
If you need to customize Valhalla's configuration to e.g. increase the allowed maximum distance for the /route POST endpoint, just edit custom_files/valhalla.json and restart the container. It won't rebuild the tiles in this case, unless you tell it to do so via environment variables.
In the case where you have a pre-built valhalla_tiles.tar package from another Valhalla instance, you can also dump that to custom_files/ and they're loaded upon container restart if you set the following environment variables: use_tiles_ignore_pbf=True, force_rebuild=False. Also, don't forget to set the md5 sum for your valhalla_tiles.tar in .file_hashes.txt.
If you want to verify that the image is working correctly, there's a small test script in ./tests. Note, it requires sudo since it touches a few things generated by the container's root user (no worries, it won't break your system):
sudo ./tests/test.sh
This project was first introduced by MichaelsJP.
The gisops/valhalla Docker image is a fantastic starting point but does not give enough control on what happens when starting the container.
The new image simply adds a new script to configure Valhalla and generate the tiles without starting the server itself, and ensures that the tools required for preparing data for Pelias are present.
NOTE: This image is based on the 3.1.2 version of Valhalla.
https://github.com/gis-ops/docker-valhalla#container-recipes
To only prepare the data without starting the server, use the following script: /valhalla/scripts/generate_only.sh instead of the default entry point.
Content type
Image
Digest
Size
127.8 MB
Last updated
over 5 years ago
docker pull strikehawk/docker-valhalla:3.1.2