use COPY --chown to stage repo (docker 17.09)
See original GitHub issueRight now, we copy and chown the repo in two layers, which doubles the size the repo takes up in the env. This used to be required. Docker 17.09 adds support for COPY --chown
to do it in one layer. So we can do this when it becomes okay to require docker 17.09 as the base version.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:14 (13 by maintainers)
Top Results From Across the Web
use COPY --chown to stage repo (docker 17.09) #164 - GitHub
Right now, we copy and chown the repo in two layers, which doubles the size the repo takes up in the env. This...
Read more >Docker Engine 17.09 release notes
Add --chown flag to ADD/COPY commands in Dockerfile moby/moby#34263; Fix cloning unneeded files while building from git repositories ...
Read more >The backlash of chmod/chown/mv in your Dockerfile - Medium
Updating ownership on a file with chown effectively results in duplicating that file and storing its new copy in a new layer. The...
Read more >Docker Copy and change owner - file permissions
A --chown flag has finally been added to COPY : COPY --chown=patrick hostPath containerPath. This new syntax seems to work on Docker 17.09....
Read more >Can I avoid or cache a `usermod` and `chown` command ...
Since Docker 17.09 and up one can add the chown flag to both COPY and ADD : COPY --chown=someuser:somegroup /foo /bar ADD --chown=someuser:somegroup...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Me and @jhamman found out that version of docker used by GKE does not support this yet, so the default install of BinderHub can’t use it (since it uses the same docker as the underlying cluster)
We have a “JupyterHub fellow”???