.dockerignore: remove unnecessary files from Docker build context #686
Conversation
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
schildbach
force-pushed
the
dockerignore
branch
from
1b37589 to
0dac978
Compare
Jacksonearl2468
approved these changes
Nov 10, 2024
This removes hidden files (including the git configuration and history!) and the docker/compose files. These files are not needed for building and running and bloat the image, can leak sensitive information and invalidate the build cache.
schildbach
force-pushed
the
dockerignore
branch
from
0dac978 to
c651abd
Compare
Contributor
Author
|
Rebased to current master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This removes hidden files (including the git configuration and history!) and the docker/compose files. These files are not needed for building and running and bloat the image, can leak sensitive information and invalidate the build cache.
Again, I tested this against my own installation.