fix(docker): use COPY --chmod to avoid duplicate layer in transcription-proxy#313
Merged
basnijholt merged 1 commit intomainfrom Jan 25, 2026
Merged
fix(docker): use COPY --chmod to avoid duplicate layer in transcription-proxy#313basnijholt merged 1 commit intomainfrom
basnijholt merged 1 commit intomainfrom
Conversation
…on-proxy The previous approach of running `chmod -R 755` after COPY created a duplicate layer (~38MB) because modifying file metadata causes Docker to store the entire directory again. Using `COPY --chmod=755` sets permissions during the copy operation, eliminating the wasted layer. The RUN command now only sets permissions on parent directories (which is essentially free).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
COPY --chmod=755to set permissions during copy instead of runningchmod -RafterwardProblem
The previous Dockerfile created two layers for the same content:
This caused Docker to store the directory twice because modifying file metadata creates a new layer.
Solution
Test plan
docker history