This repository was archived by the owner on May 26, 2023. It is now read-only.
Revert "Revert "Fix: docker failure on M1 macs"" #119
Merged
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's this PR do?
Reverts a previous revert of a PR that fixed a docker build issue that was merged to master. In other words, this PR restores PR #118.
Why are we doing this? How does it help us?
After it was merged to master, PR #117 seemingly caused the failure of a Tribune rundeck job that updates a spreadsheet each day with stats from our database. However, after discussion among the Tribune's engineering team, it remains unclear why that merge would have caused that rundeck job to fail. We theorize that the rundeck job's failure – while still mysterious – may have been a coincidence.
How should this be manually tested?
How should this change be communicated to end users?
Are there any smells or added technical debt to note?
What are the relevant tickets?
Have you done the following, if applicable:
(optional: add explanation between parentheses)
TODOs / next steps: