The build was hard code to amd64 for docker build

[gyliu513]

Describe the bug
A clear and concise description of what the bug is.

After I run make docker-otelcontribcol on my mac, I found the binary name was otelcontribcol_linux_amd64, seems the makefile is hardcoding the GOARCH as amd64 https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/Makefile#L241 , any reason why? Thanks!

Steps to reproduce
If possible, provide a recipe for reproducing the error.

What did you expect to see?
A clear and concise description of what you expected to see.

What did you see instead?
A clear and concise description of what you saw instead.

What version did you use?
Version: (e.g., v0.4.0, 1eb551b, etc)

What config did you use?
Config: (e.g. the yaml config file)

Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

Additional context
Add any other context about the problem here.

[codeboten]

I think the docker make target is intended specifically to build a collector to run inside a container, make otelcontribcol is the target used to compile locally.

[gyliu513]

Thanks @codeboten , but still have a question: why hardcoding docker build to amd64? With docker build, it should also support multi-arch as well.

[codeboten]

It's a good question, based on git blame it looks like the decision was made over 2 years ago. I'm not sure why

[TylerHelmuth]

@gyliu513 Are you free to update the docker-otelcontribcol target to support more architectures?

[gyliu513]

@TylerHelmuth Yes, glad to help. Will fix early next week.

[dmitryax]

#12217 doesn't seem like introduced multi arch image creation

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.