x86-64 binaries in the arm64 image

[slapula]

What steps did you take:
In an effort to learn more about Carvel tools, I wanted to deploy kapp-controller to my raspberry pi cluster running k0s. I found that initial arm64 support was merged into the develop branch last month based on the work done in #680. I forked this repository and created a tag with the cherry-picked commits included so I could build an image that works for my cluster.

What happened:
The build process (in it's current form in develop) does not produce a kapp-controller binary that is arm64. Here's a peak inside the container:

kapp-controller [ / ]$ file kapp-controller
kapp-controller: ELF executable, 64-bit LSB x86-64, static, not stripped
kapp-controller [ / ]$ file kapp           
kapp: ELF executable, 64-bit LSB arm64, static, not stripped
kapp-controller [ / ]$ file kapp-controller-sidecarexec 
kapp-controller-sidecarexec: ELF executable, 64-bit LSB x86-64, static, not stripped
kapp-controller [ / ]$ file kbld                        
kbld: ELF executable, 64-bit LSB arm64, static, not stripped
kapp-controller [ / ]$ ls

What did you expect:
I expected arm64 image to contain arm64 compatible binaries when using the develop branch

Anything else you would like to add:
I will follow up this issue with a PR shortly since the problem is directly related to a typo in the Dockerfile.

Environment:

• kapp Controller version (execute kubectl get deployment -n kapp-controller kapp-controller -o yaml and the annotation is kbld.k14s.io/images):
• Kubernetes version (use kubectl version)

---

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.