Closed hinricht closed 1 year ago
This was a bug that I fixed today with v0.5.5. Can you retry with the current version?
Surprisingly, it was not noticed by cargo test
, even though the tests cover the code. Probably something to do with it being wrapped around a lazy_static!
macro.
Thanks, pulling the latest image fixed the issue:
$ docker run --rm versatiles/versatiles:latest-alpine versatiles serve '[osm]https://storage.googleapis.com/versatiles/download/planet/europe/germany/berlin-20230101.versatiles'
/tiles/osm/* <- https://storage.googleapis.com/versatiles/download/planet/europe/germany/berlin-20230101.versatiles
server starts listening on 127.0.0.1:8080
Btw, I was also able to serve a local versatiles file with docker run -v $(pwd)/data/:/data --rm versatiles/versatiles:latest-alpine versatiles serve '/data/berlin-20230101.versatiles'
:+1:
I'm trying to get started using Docker locally and am happy to provide a tutorial once I succeed. I'd like to start with little extra setup as possible (i.e. without building the additional image), to get a first impression.
Iiuc, I should be able to start versatile with
But it fails with:
Passing
-e RUST_BACKTRACE=full
doesn't provide any more useful information.Maybe I'm doing sth wrong here, can you please point me in the right direction ?