chore: multi-arch support with buildx in all Dockerfiles

[kahirokunn]

Proposed Changes

I deployed a docker image built on M1 mac to an intel cluster and got a cpu architecture error.
Now that support for both amd and arm is expanding, I think it is better for users to use buildx to build both to try out the sample.

[netlify]

✅ Deploy Preview for knative ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	9a3b5b4
🔍 Latest deploy log	https://app.netlify.com/sites/knative/deploys/64e2ef93a04b1b00083f15f6
😎 Deploy Preview	https://deploy-preview-5273--knative.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[knative-prow]

Welcome @kahirokunn! It looks like this is your first PR to knative/docs 🎉

[abrennan89]

@knative/serving-reviewers

[psschwei]

The new command failed for me with the following output:

[+] Building 0.0s (0/0)                                                                                  
ERROR: multiple platforms feature is currently not supported for docker driver. 
Please switch to a different driver (eg. "docker buildx create --use")

whereas the original commands worked without issue. If we're going to update it to use buildx, we'll need some more set up info since it doesn't work out of the box.

[csantanapr]

I think adding a link to the buildx should be enough.

[kahirokunn]

is like this?

[kahirokunn]

If correct, consolidate into one commit.

[psschwei]

Personally, I think I'd rather leave the default as-is and provide a link to buildx for those who need to do a multiarch build (which won't be everyone)

[kahirokunn]

If you let people use buildx from the beginning, the container image will run on many people's PCs.
You will not have to worry about CPU architecture errors.
Therefore, buildx is also a good choice.

[github-actions]

This Pull Request is stale because it has been open for 90 days with
no activity. It will automatically close after 30 more days of
inactivity. Reopen with /reopen. Mark as fresh by adding the
comment /remove-lifecycle stale.

[kahirokunn]

keep

[dprotaso]

The Dockerfile needs to be updated to support multi arch first

ie.
098a9da

[skonto]

@kahirokunn gentle ping, are you still planning to update it?

[kahirokunn]

@dprotaso @skonto I have addressed the points raised. How about now?

[skonto]

I will test the updates thanks @kahirokunn. We do not want this for the rest of the samples? I think we need proper image build instructions for all no?

[kahirokunn]

Do you wish to buildx all images in this repository?

[skonto]

It would be nice to have build options or maybe a separate page for building alternatives instead of copying the same command everywhere.

[skonto]

@dprotaso @psschwei wdyth? Should we re-write docs also to include builds with docker buildx for the other samples too?

[psschwei]

@dprotaso @psschwei wdyth? Should we re-write docs also to include builds with docker buildx for the other samples too?

I think I'm still slightly in favor of leaving things as is, with maybe a link out to buildx and/or other alternatives (with the view towards minimizing changes as these samples aren't really actively maintained). But, that said, I don't feel particularly strongly about it (I also don't use a Mac), so if we do decide we should update, that's fine too.

But if we do update, we should update all, I think.

[kahirokunn]

@psschwei Okay, I will update all.

[kahirokunn]

done. how about now?

[kahirokunn]

@psschwei I would appreciate a review before conflicts arise. thx.

[psschwei]

Sorry about that, I missed the notification for this one one...

/lgtm
/approve

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kahirokunn, psschwei

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [psschwei]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment