Closed answerquest closed 5 months ago
Smth must’ve changed in 23.04 then I guess. Good chance to get rid of that entirely, it’s a pretty annoying logic.. or if you want, you can fix it.
Hi, I went ahead with default flow, building the image without supplying any build args, and it worked fine at downloading pbf, building the valhalla tiles in the local persistent volume folder, and running it. I checked the permissions of the contents of persistent volume and they're all under the local user only:
-rw-rw-r-- 1 azureuser azureuser 1451549425 Jan 18 13:20 india-latest.osm.pbf
drwxrwxr-x 2 azureuser azureuser 4096 Jan 18 13:22 admin_data
-rw-rw-r-- 1 azureuser azureuser 136 Jan 18 14:14 duplicateways.txt
drwxrwxr-x 5 azureuser azureuser 4096 Jan 18 14:33 valhalla_tiles
-rw-rw-r-- 1 azureuser azureuser 65 Jan 18 14:33 file_hashes.txt
-rw-rw-r-- 1 azureuser azureuser 3817789440 Jan 18 14:34 valhalla_tiles.tar
So going ahead with default stuff. Will close this issue.
Well, then it must be Azure which registers a user within the docker container with UID/GID 1000. To anyone reading this in the future: try things locally, those weird services add way too many obscure layers..
OS: Ubuntu 20.04.6 LTS (GNU/Linux 5.15.0-1045-azure x86_64)
It's a server on Azure.
This fails with logs:
From the readme, it was advised that we pass in the local user / group ids as build args so that permissions for persistent volume stay local or something.. the link in readme is no longer working also.