Closed arne-cl closed 4 years ago
This seem to be two issues, not one.
Permissions for /mnt/pelias
can be fixed in the Dockerfile
of pip-service
, while permissions for /data
(or /data/whosonfirst
) can only be fixed in Dockerfile
of pelias/baseimage
(before VOLUME "/data"
).
I got the same issue. You have to run the container image with the UID/GUID 1000. On Kubernete, it will be define like this:
securityContext:
runAsUser: 1000
runAsGroup: 1000
fsGroup: 1000
@leangeder all the Pelias docker images default to using uid 1000 (as they define a pelias user with uid 1000 and switch to it with the USER
directive).
However it might be interesting to add runAsUser
and the other settings in https://github.com/pelias/kubernetes, so that people can change it if they'd like.
I think we determined this (as it pertains to the PIP service itself) ended up being a local filesystem permissions issue. We try to make the Pelias docker project runner fix or detect those issues where possible.
For kubernetes, if this is still necessary, please open a new issue in https://github.com/pelias/kubernetes
With the current Dockerfile, it is not possible to use the
download
command ofpip-service
(needed for it'sinitContainer
in a Kubernetes setup).Note, that this problem doesn't seem to occur in Kubernetes when an
emptyDir
is mounted to/data
(instead of using a PVC), cf. pelias/kubernetes#79.