Closed JesperWe closed 1 year ago
Describe the bug The v3.1.0 initial Docker build fails with/var/install/libosmium does not appear to contain CMakeLists.txt
v3.1.0
/var/install/libosmium does not appear to contain CMakeLists.txt
Screenshots
> .\sequentially-generate-planet-mbtiles--win-amd64-v3.1.0.exe -c .\config.json 2023/04/11 12:28:04 using tileserver-gl-basic style target 2023/04/11 12:28:04 # 2023/04/11 12:28:04 loggers.go:26: # 2023/04/11 12:28:04 # 2023/04/11 12:28:04 sequentially-generate-planet-mbtiles started: &{srcFileProvided:false PbfFile:C:\Users\admin\Downloads\data\pbf\planet-latest.osm.pbf WorkingDir:C:\Users\admin\Downloads\data OutDir:C:\Users\admin\Downloads\tiles ExcludeOcean:false ExcludeLanduse:false TilemakerConfig:C:\Users\admin\AppData\Local\sequentially-generate-planet-mbtiles\tilemaker\resources\config-openmaptiles.json TilemakerProcess:C:\Users\admin\AppData\Local\sequentially-generate-planet-mbtiles\tilemaker\resources\process-openmaptiles.lua MaxRamMb:16000 OutAsDir:false SkipSlicing:false MergeOnly:false SkipDownload:false} 2023/04/11 12:28:04 git repo C:\Users\admin\AppData\Local\sequentially-generate-planet-mbtiles\gdal already exists, skipping clone 2023/04/11 12:28:04 git repo C:\Users\admin\AppData\Local\sequentially-generate-planet-mbtiles\osmium\osmium-tool already exists, skipping clone 2023/04/11 12:28:04 git repo C:\Users\admin\AppData\Local\sequentially-generate-planet-mbtiles\osmium\libosmium already exists, skipping clone 2023/04/11 12:28:04 git repo C:\Users\admin\AppData\Local\sequentially-generate-planet-mbtiles\tilemaker already exists, skipping clone 2023/04/11 12:28:04 git repo C:\Users\admin\AppData\Local\sequentially-generate-planet-mbtiles\tippecanoe already exists, skipping clone failed to get console mode for stdin: The handle is invalid. [+] Building 1.4s (11/14) => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 758B 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [internal] load metadata for docker.io/library/debian:bookworm-slim 0.9s => [ 1/10] FROM docker.io/library/debian:bookworm-slim@sha256:e54d36fb429ae2f8e102d5903e60aeb689bb26056ca2930f9d622ced90fbe730 0.0s => [internal] load build context 0.0s => => transferring context: 42.48kB 0.0s => CACHED [ 2/10] RUN apt-get update 0.0s => CACHED [ 3/10] RUN apt-get update && apt-get install -y libosmium2-dev libprotozero-dev libboost-program-options-dev libbz2-dev zlib1g 0.0s => CACHED [ 4/10] RUN mkdir /var/install 0.0s => CACHED [ 5/10] WORKDIR /var/install 0.0s => CACHED [ 6/10] COPY libosmium libosmium 0.0s => ERROR [ 7/10] RUN cd libosmium && mkdir build && cd build && cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_EXAMPLES=OFF -DBUILD_TESTING 0.3s ------ > [ 7/10] RUN cd libosmium && mkdir build && cd build && cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_EXAMPLES=OFF -DBUILD_TESTING=OFF -DINSTALL_PROTOZERO=ON .. && make: #11 0.315 CMake Warning: #11 0.315 Ignoring extra path from command line: #11 0.315 #11 0.315 ".." #11 0.315 #11 0.315 #11 0.315 CMake Error: The source directory "/var/install/libosmium" does not appear to contain CMakeLists.txt. #11 0.315 Specify --help for usage, or press the help button on the CMake GUI. ------ executor failed running [/bin/sh -c cd libosmium && mkdir build && cd build && cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_EXAMPLES=OFF -DBUILD_TESTING=OFF -DINSTALL_PROTOZERO=ON .. && make]: exit code: 1 2023/04/11 12:28:06 containers.go:48: failed to build osmium container: exit status 1
Desktop (please complete the following information):
For posterity, this was caused by an earlier git clone failing with Filename too long.
Fixed by runninggit config --system core.longpaths true as Administrator, then deleting all files and starting over again.
git config --system core.longpaths true
Describe the bug The
v3.1.0
initial Docker build fails with/var/install/libosmium does not appear to contain CMakeLists.txt
Screenshots
Desktop (please complete the following information):