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

Can we publish the list of distroless supported architectures? #346

Closed
yuwenma opened this issue Apr 12, 2019 · 7 comments
Closed

Can we publish the list of distroless supported architectures? #346

yuwenma opened this issue Apr 12, 2019 · 7 comments

Comments

@yuwenma
Copy link

yuwenma commented Apr 12, 2019

Hi,

We are trying to use distroless as the base image for kubernetes images (See details here) These containers can run in different architectures (am64, arm32v6,arm64v8,ppc64le, s390x).

I couldn't find any resource giving the full list of distroless supported architectures, so I think maybe I should file this issue. Can we have an official list of distroless supported architectures?

I also found issue #222. Is there any plans on supporting the following architectures: am64, arm32v6,arm64v8,ppc64le, s390x ?

@yuwenma
Copy link
Author

yuwenma commented Apr 12, 2019

/cc @dlorenc @chanseokoh

@tallclair
Copy link

See this comment: #259 (comment)

We're just using distroless:static in Kubernetes, which doesn't have any binary components, so doesn't need multi-architecture builds

@yuwenma
Copy link
Author

yuwenma commented Apr 12, 2019

@tallclair Thanks Tim. Then I'm good to move forward. Will keep this issue open to track further discussions about publishing an official architecture list.

@chanseokoh
Copy link
Member

FTR: bazelbuild/rules_docker#300

X-ref: #406 #569

@rpsene
Copy link

rpsene commented Aug 18, 2020

@chanseokoh not arch agnostic:

Screen Shot 2020-08-18 at 15 20 43

@chanseokoh
Copy link
Member

chanseokoh commented Aug 18, 2020

Yup, certainly, the image configuration contains platform information. What I'm telling you is that, for distroless/static, everything else except the image metadata is most likely platform-agonistic.

@jonjohnsonjr
Copy link
Contributor

The actual contents of the image aren't platform specific -- I assume the config file values are just a historical curiosity.

I ran into something similar in google/go-containerregistry#751 where we accidentally were omitting those fields and it worked for everything except for windows... if rules_docker allows us to just drop the architecture, that might be enough to get container runtimes to be happy?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants