You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Docker API for copying an archive to a container has a flag CopyUIDGID.
You could therefore chown a file locally to whatever UID/GID required, and this ownership will be retained in the container. This simulates an equivalent of
COPY --chown=user:group myfile /path/in/container/myfile
# OR
COPY myfile /path/in/container/myfile
RUN chown user:group myfile
The text was updated successfully, but these errors were encountered:
@mutantcornholio Would something like this work for your use case? Specifically setting the UID/GID on the file locally to the desired UID/GID on the container?
Tracking this issue at the moment mafintosh/tar-fs#108. Setting the file ownership permissions manually and doing a docker cp into the container correctly preserves the permissions. From my testing it seems the tar-fs library is what's losing the ownership permissions.
The Docker API for copying an archive to a container has a flag CopyUIDGID.
You could therefore chown a file locally to whatever UID/GID required, and this ownership will be retained in the container. This simulates an equivalent of
The text was updated successfully, but these errors were encountered: