-
Notifications
You must be signed in to change notification settings - Fork 120
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(build): avoid docker cache contamination and invalidation (#4254)
* imp(build): reduce docker cache invalidation Use scoped caching and more file ignores to reduce cache invalidation * fix(build): add entrypoint.sh as a required file * fix(build): do not logout if the build takes too long * Add 'doc comment' about .dockerignore Co-authored-by: Deirdre Connolly <durumcrustulum@gmail.com>
- Loading branch information
1 parent
93f40fd
commit 8b68651
Showing
2 changed files
with
27 additions
and
8 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,23 @@ | ||
target | ||
Dockerfile | ||
.dockerignore | ||
.git | ||
.github | ||
.gitignore | ||
# Before the docker CLI sends the context to the docker daemon, it looks for a file | ||
# named .dockerignore in the root directory of the context. If this file exists, the | ||
# CLI modifies the context to exclude files and directories that match patterns in it. | ||
# | ||
# You may want to specify which files to include in the context, rather than which | ||
# to exclude. To achieve this, specify * as the first pattern, followed by one or | ||
# more ! exception patterns. | ||
# | ||
# https://docs.docker.com/engine/reference/builder/#dockerignore-file | ||
|
||
# Exclude everything: | ||
# | ||
* | ||
|
||
# Now un-exclude required files and folders: | ||
# | ||
!.cargo | ||
!*.toml | ||
!*.lock | ||
!tower-* | ||
!zebra-* | ||
!zebrad | ||
!docker/entrypoint.sh |
This file contains 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