search

lambdajack / sequentially-generate-planet-mbtiles

Generate vector tiles for the entire planet on relatively low spec hardware.
https://wiki.openstreetmap.org/wiki/Sequentially-generate-planet-mbtiles
MIT License
100 stars 15 forks source link

mbtiles can't be merged #4

Closed Haves1001 closed 2 years ago

Haves1001 commented 2 years ago

In the final step of the process (when the mbtiles are being merged) the program tries to use a docker container that doesn't exist locally not on docker hub:

Unable to find image 'sequential-tippecanoe:latest' locally
docker: Error response from daemon: pull access denied for sequential-tippecanoe, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.

I didn't remove any build docker container locally though.

Haves1001 commented 2 years ago

This might have been caused by me interrupting the initial build of the container when I realised that I needed to free up more disk space. I'm wondering how the information that the container has been build is persisted?

lambdajack commented 2 years ago

Hi again,

Sequentially-generate-planet-mbtiles uses your local docker installation to manage all necessary persistence for it. It will basically ask docker to run a docker container associated with the tag that sequentially-generate-planet-mbtiles previously built.

Sequentially-generate-planet-mbtiles will try to build the relevant container every time it is run. If docker itself reports that the file is built then it simply moves on to the next thing.

I have just run this to check and it worked as expected.

I would try deleting the container using docker directly and starting again.

What OS are you using? are you running with correct permissions (sudo may be needed etc).

lambdajack commented 2 years ago

P.s. I am currently working on adding the dependencies as sub-modules for version safety. (though that does not appear to the problem here).

Haves1001 commented 2 years ago

This is indeed quite weird. It worked well when I manually build the docker container (without deleting any containers) and executed the mbtiles merge afterwards. I have been running this on my Ubuntu workstation with the right permissions using sudo.

I think this might be caused by me interrupting the initial build of the container. Weird though that the next run didn't rebuild the image. All the other images were build correctly. We can close this though, I think this is a weird corner case. Thank you for your quick response :)