host user running docker requires UID of 1000 for elasticsearch about docker HOT 10 CLOSED

actually all docker containers require a UID of 1000 it seems, not that it matters much

from docker.

Yeah for sure, permissions inside permissions, can be a nightmare.

I thought I'd fixed this last year, we haven't had many reports recently. How it's supposed to work is that the pelias command detects your UID automatically so you shouldn't have to do anything.

from docker.

can't see much in the pelias commands other than the deprecated DOCKER_USER.

the pelias command detects your UID automatically so you shouldn't have to do anything.

but how would that work even? it detects your UID but it can't take that for the docker-internal user, that would have to be decided in the image building when creating the user. we could change the permissions with the pelias command to 1000:1000 but not without sudo. (also would be strange, my data dir would then be owned by the host user overpass :D).

I think everyone got lucky so far, always having run this with the machine's first user:)

from docker.

I had a similar use case before and had to change our valhalla image to accommodate for that:
https://github.com/gis-ops/docker-valhalla/blob/a503d556a75661a644c25b16fa82eafa89b3f963/Dockerfile#L44-L50

definitely not arguing that's an option for your docker recipes, it's also a total nightmare.

from docker.

You can specify the docker user at runtime too

from docker.

huh.. let me research hahah 😅

from docker.

• https://github.com/pelias/docker/blob/master/lib/env.sh
• https://github.com/pelias/docker/blob/master/projects/planet/docker-compose.yml#L115

from docker.

ah right, totally forgot about that..

I guess that's what DOCKER_USER was for?

from docker.

https://github.com/pelias/docker/blob/master/lib/env.sh

thanks!! didn't find that! yes, that should definitely do it. I'll just quietly close this issue and admit my idiot mistake of not using the provided docker-compose.yml..

from docker.

Haha all good, permissions are the most common issue we get, I might spend some more time on the pelias system check command to see if it can detect issues like this automatically.

from docker.