-
Notifications
You must be signed in to change notification settings - Fork 408
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
ko should produce multi-platform images #6
Comments
Blocked by: google/go-containerregistry#119 Some thoughts also here under "Fat ko": google/go-containerregistry#254 |
The general idea for this was to drive the platform selection via the base image. Specifying a manifest list as the base image should produce a manifest list. If you want to build for a single platform, you could specify that platform's image. I like this approach because we don't have to add any additional configuration or flags or anything, it's totally data-driven. One drawback is that it might be surprising that if you specify e.g. We currently just pass through environment variables to This will be a bit of a pain to rework some of We'll need to do something similar to |
May I ask I question? Am I must export the env |
@zxDiscovery correct, if you use a ppc64le specific image, you don''t need to export GOARCH anymore. Let me know if that doesn't work for you. |
I use ko to build the ppc64le image on ppc64le platform, but the image can't work normally when I didn't export
After I export
|
@zxDiscovery If you're not overriding the base image, it will use To demonstrate, building an image containing
|
I wonder if we'll need something like https://github.com/karalabe/xgo to support CGO for this 🤔 |
#38 has landed but we should document this. |
update references to imjasonh/setup-ko
Right now we assume amd64/linux and use distroless.
This is blocked on full manifest list support in the library, but ideally supplying a multi-platform base image would produce a multiplatform ko image.
(this is mostly a placeholder for reference until I flesh this out more)
The text was updated successfully, but these errors were encountered: