fix: specify amd64 target platform for watchdog image #57
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
added 3 commits
December 23, 2022 13:44
|
Was this closed intentionally? This pull request is critical for deploying from an M-series Mac |
|
I had this exact issue on developing with an M1 mac. I don't see an issue with this approach. |
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.
Description
Specifies what CPU architecture the image should be built for. This change sets the target platform to match the default Fargate task definition CPU architecture. I have tested watchdog build using an ARM64 system, with working server results.
Related
I believe this resolves the following issues:
Disclosure
While I don't believe this should be a breaking change, I have not tested build from non-arm64 system.