COPY command ignores USER, sets file ownership to root

[nunofgs]

There are multiple issues submitted to the docker/docker about this.

My use case is similar to:

FROM ubuntu
RUN adduser foo
USER foo
ADD . /foo

I believe the USER instruction should affect any subsequent COPY and ADD instructions to avoid having to always chown any copied directories/files.

Any chance dockramp could support this use case?

[jlhawn]

dockramp could support this if the API endpoint did. I think it's a good behavior to have, but there still might be a desire to copy files with ownership other than the current USER value.

I was thinking of something that looks like:

COPY --chown="user:group" foo/bar /baz

It would allow you to specify ownership per-COPY. Again, it relies on the Docker API endpoint used by COPY to support this functionality.

[iambowen]

I think it's a pretty wired setting for not giving options to set the file ownership and permission.
Can we just make some improvement on this?

[Rishamdeep]

This issue has been resolved.
Starting with Docker 17.09.0-ce (2017–09–26) ADD/COPY commands now support the --chown flag in Dockerfile:

Example of usage:
COPY --chown=docker:docker source /path/to/destination