1b5f48f118
The BRouter host's trails user is non-root without sudo, so osmium-tool can't be apt-installed. Ship osmium.Dockerfile (built on first use) and run osmium in a container with the work dir bind-mounted (native I/O, negligible overhead on Linux). python3/curl/gzip/sha256sum remain on the host. Correct the README disk figure to the /home free space (~595 GB). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
15 lines
686 B
Docker
15 lines
686 B
Docker
# Minimal osmium-tool image for the POI extract pipeline. The BRouter host runs
|
|
# a non-root `trails` user with no sudo, so osmium can't be apt-installed on the
|
|
# host — poi-extract.sh runs it in this container instead (docker-group rights
|
|
# are available). Big files are bind-mounted, so I/O is native; the container
|
|
# adds no meaningful CPU/throughput overhead on Linux.
|
|
#
|
|
# Built on first use by poi-extract.sh (tag: trails-osmium:local). Self-hosters
|
|
# get identical behavior without touching system packages.
|
|
FROM debian:bookworm-slim
|
|
|
|
RUN apt-get update \
|
|
&& apt-get install -y --no-install-recommends osmium-tool \
|
|
&& rm -rf /var/lib/apt/lists/*
|
|
|
|
ENTRYPOINT ["osmium"]
|