-
Notifications
You must be signed in to change notification settings - Fork 863
Fix building arm64 docker image #7093
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
70abceb
to
291187e
Compare
|
@Groxx is looking at go 1.24 upgrade. Once that's done we can merge this PR. |
@tamalsaha Looks like go1.24 migration will not be trivial at this point. #7111 |
Signed-off-by: Tamal Saha <tamal@appscode.com>
I have downgraded dockerize to v0.9.3 which seems to compile using 1.23.4 |
…ze (cadence-workflow#7149) Hopefully fixes cadence-workflow#7093 in a simpler way. Tested with `docker run ... dockerize --help` on two machines with arm64 and amd64 and it seems to work, though the `ARG TARGETARCH` appears to require `docker buildx` or manual entry. That's a bit awkward for my test-machines (no buildx), but seems likely fine as github actions uses that for build-and-push. And checked the final in-container docker.yml file that it generates, and it both ran fine and looks essentially identical. So this seems safe enough. If we have issues, people can downgrade and we can revert (though revert will not restore a working arm image for new attempts. but that's also broken now).
hmm. did this auto-close because of my commit message...? if so, I should see if I can disable that for myself, or word a lot more carefully or something :\ I didn't mean to close this, though it probably can be closed. |
No worries. Your fix works. |
What changed?
Using correct version of dockerize binary in docker image for ARM64
Why?
How did you test it?
Potential risks
Release notes
Documentation Changes