-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Multi-arch docker images. #496
Labels
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Comments
Johannestegner
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
May 15, 2020
This issue is stale because it has been labeled with inactivity. |
github-actions
bot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and will be auto-closed.
label
Mar 22, 2021
krol3
added
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and will be auto-closed.
labels
Mar 22, 2021
knqyf263
added
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
labels
Mar 22, 2021
I think we can easily do that with GoReleaser. You can see a good example here. |
knqyf263
added
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
and removed
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
labels
Mar 22, 2021
See the release note. |
josedonizetti
pushed a commit
to josedonizetti/trivy
that referenced
this issue
Jun 24, 2022
…ation (aquasecurity#496) Resolves aquasecurity#452 Signed-off-by: Liam Galvin <liam.galvin@aquasec.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Hi there!
I would like to request multi-arch docker images, seeing the releases page have basically all architectures one could wish for, this should not be a huge issue to implement!
I would think that at the least aarch64 and possibly a couple of the 32b ARM cpu's would be the initial most-required versions if this is to be implemented, and if there is no experience in the field of multi-arch images I'd recommend taking a look at buildx with qemu support.
If you need any type of help with setting something up, let me know and I'll happily help!
Until implemented or requested for takedown:
As of now (due to me using both amd64 and arm64 machines in my ci-fleet) I created an image for amd64 and aarch64 cpus which could be found here (for anyone who requires it til it is implemented on the official channel!): https://hub.docker.com/repository/docker/jitesoft/trivy
Image is built from source on native machines and are ofc scanned with Trivy to make sure there are no vulnerabilities! ;)
The text was updated successfully, but these errors were encountered: