Skip to content
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

Multiarch docker images #2292

Closed
rur0 opened this issue Jun 15, 2020 · 4 comments · Fixed by #2948
Closed

Multiarch docker images #2292

rur0 opened this issue Jun 15, 2020 · 4 comments · Fixed by #2948
Labels
help wanted Features that maintainers are willing to accept but do not have cycles to implement

Comments

@rur0
Copy link

rur0 commented Jun 15, 2020

Requirement - what kind of business use case are you trying to solve?

Ability to utilize multiarch images

Problem - what in Jaeger blocks you from solving the requirement?

I have a rpi k3s (arm64) cluster that I use to run a web app written in golang, and I would like to use jaeger for tracing on it. I have compiled jaeger-operator and got it running on the cluster, however when it pulls the main jaeger docker image- it errors out with 'exec format'.

Proposal - what do you suggest to solve the problem or improve the existing situation?

Build and upload multiarch images to official docker repo

Any open questions to address

@ghost ghost added the needs-triage label Jun 15, 2020
@yurishkuro yurishkuro added help wanted Features that maintainers are willing to accept but do not have cycles to implement and removed help wanted Features that maintainers are willing to accept but do not have cycles to implement needs-triage labels Jun 15, 2020
@yurishkuro
Copy link
Member

Are you referring to a single image somehow being multi-arch, or to multiple images? There would be a lot of manual work on creating individual docker hub repo for each one permutation.

@pavolloffay
Copy link
Member

@rur0 thanks for creating the issue.

This has been created from jaegertracing/jaeger-operator#1086.

I think he is referring to https://docs.docker.com/buildx/working-with-buildx/. It seems that a single image can have multiple architectures. When the client requests the image from the registry it gets multiple manifests. Then the client chooses the right image.

Other resources: https://www.youtube.com/watch?v=SYJgkkjqd7s

@rur0 would you like to contribute this?

@rur0
Copy link
Author

rur0 commented Jun 16, 2020

@pavolloffay Yes

@Jingzhao123
Copy link

@MrXinWang

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Features that maintainers are willing to accept but do not have cycles to implement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants