On Wed, Dec 2, 2015 at 9:10 PM, Taylor Braun-Jones <tay...@braun-jones.org> wrote: > My use case it running git clone inside a docker container with > `docker run --user $(id -u):$(id -g) --volume /foo:/foo ...`. I want > all /foo/* file creation/access from inside the Docker container to be > done as the current uid/gid of the host system. > > Steps to reproduce: > > mkdir /tmp/docker-git > cat > /tmp/docker-git/Dockerfile <<EOF > FROM ubuntu > RUN apt-get update && apt-get install -y git-core > EOF > docker build -t git /tmp/docker-git/ > docker run --user $(id -u):$(id -g) git git clone > https://github.com/git/git.git /tmp/git > # fatal: unable to look up current user in the passwd file: no such user
It probably helps if you could get the stack trace to this message (printed from function xgetpwuid_self). I haven't checked if my personal laptop has docker to reproduce this.. In general we won't ask passwd if the user specifies name/email in the config file. But I still don't see why git-clone needs that info in the first place. -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
