[CPSRE-1342] Refactored Dockerfile #4386
Closed
Conversation
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
✅ Deploy Preview for gallant-galileo-14878c canceled.
|
nick-funk
approved these changes
Nov 6, 2023
kabeaty
approved these changes
Nov 7, 2023
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.
What does this PR do?
By leveraging a multi-stage build within the Dockerfile, we can add additional build tools (to support a future arm64 or multiarch build) while still achieving a smaller final image size:
These changes will impact:
What changes to the GraphQL/Database Schema does this PR introduce?
N/A
Does this PR introduce any new environment variables or feature flags?
Nope
If any indexes were added, were they added to
INDEXES.md?N/A
How do I test this PR?
Pull the changes and build from source as normal. Compare the final image size to the current develop default.
Where any tests migrated to React Testing Library?
No
How do we deploy this PR?
No additional considerations are necessary.