Using OSRM backend in Docker for routing bicycles

Question

I am currently setting up the OSRM routing backend in Docker as described in the Github Repository:
https://github.com/Project-OSRM/osrm-backend

Currently, the routing service is working successfully for routing cars (using the car.lua file) and I can send a request to the service inside the Docker container to get the route information.

However, I cannot get the service running for bicycle routes. In the Github Repository, there is a bicycle.lua which I use instead of the car.lua file. My docker-compose.yaml file is structures as follows:

version '3'
services
  routing-init:
    container_name: 'routing-init'
    image: osrm/osrm-backend
    volumes:
      - "./:/data"
      - "./bicycle.lua:/opt/bicycle.lua"
      - "./lib:/opt/lib"
    command: bash -c "osrm-extract -p /opt/bicycle.lua /data/niedersachsen-latest.osm.pbf && osrm-partition /data/niedersachsen-latest.osm.pbf && osrm-customize /data/niedersachsen-latest.osm.pbf"
    tty: true

If I run this in Docker, I get following error message:

docker-compose up routing-init
Recreating routing-init ... done
Attaching to routing-init
routing-init      | [info] Parsed 0 location-dependent features with 0 GeoJSON polygons
routing-init      | [info] Using script /opt/bicycle.lua
routing-init      | [info] Input file: niedersachsen-latest.osm.pbf
routing-init      | [info] Profile: bicycle.lua
routing-init      | [info] Threads: 16
routing-init      | [info] Parsing in progress..
routing-init      | [info] input file generated by osmium/1.14.0
routing-init      | [info] timestamp: 2023-04-19T20:21:32Z
routing-init      | [info] Using profile api version 4
routing-init      | [info] Parse relations ...
routing-init      | [info] Parse ways and nodes ...
routing-init      | [info] Using profile api version 4
routing-init      | [info] Using profile api version 4
routing-init      | [info] Using profile api version 4
routing-init      | [info] Using profile api version 4
routing-init      | [info] Using profile api version 4
routing-init      | TBB Warning: Exact exception propagation is requested by application but the linked library is built without support for it
routing-init      | [info] Using profile api version 4
routing-init      | [info] Using profile api version 4
routing-init      | [info] Using profile api version 4
routing-init      | [info] Using profile api version 4
routing-init      | [info] Using profile api version 4
routing-init      | [info] Using profile api version 4
routing-init      | [info] Using profile api version 4
routing-init      | [info] Using profile api version 4
routing-init      | [info] Using profile api version 4
routing-init      | [info] Using profile api version 4
routing-init      | terminate called after throwing an instance of 'tbb::captured_exception'
routing-init      |   what():  lua: error: /opt/lib/traffic_signal.lua:12: attempt to index global 'traffic_lights' (a nil value)
routing-init      | bash: line 1:     7 Aborted                 (core dumped) osrm-extract -p /opt/bicycle.lua /data/niedersachsen-latest.osm.pbf
routing-init exited with code 134

Using OSRM backend in Docker for routing bicycles

0 Answers0