Ricardo Wurmus <rek...@elephly.net> skribis: > Pierre Neidhardt <m...@ambrevar.xyz> writes: > >> Ricardo Wurmus <rek...@elephly.net> writes: >> >>> I suppose /etc/pam.d/ also needs to be in the container. >> >> Tried it, same error. >> >>>> What about defaulting to 1000? It's rather common, so I guess that >>>> would be anonymous enough and "just work". >>> >>> Would it make sense to map the current user’s UID into the container >>> instead of using a fixed UID? >> >> We have a "--user" option, so we could use the current user's UID when >> --user is not specified, 1000 otherwise. >> Or better: add a --uid CLI option. > > I can see confusion coming from the existence of both “--user” and > “--uid”. Maybe “--user” could take an optional argument, with the > default being the current user. Without “--user” we’d use UID 1000.
Currently, without --user, we keep the current user’s name. So it would actually be consistent to inherit its UID as well. And with ‘--user’, we’d use the given user name and UID 1000. (Essentially what Pierre proposed above.) Thoughts? :-) Ludo’.
