-
Notifications
You must be signed in to change notification settings - Fork 633
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
buildx support builds unwanted image with OS and architecture unkown/unknown #1732
Comments
Interesting. I'm not so deep in the buildx integration, which is a recent addition. Do you require to use buildx or would the traditional way of building the image also good enough ? (which relies on the architecture of the build system though). What buildx command are using concrete with |
Hi @rhuss, the traditional way would be enough for our use case. We switched to buildx as we had problems with the traditional way, as you called it. One of my team mates replaced the Docker Maven Plugin by the jib plugin, as we where under high pressure. Can I help you with other information? |
@obfischer : It's quite strange because other people are also using buildx and no one has reported a problem like this. Could you please provide these?
|
Hi @rohanKanojia, this was a freelancing project and the project finished this week. So I don't have access to the code. But the problem was reproducable on Mac, Windows and Linux. As I can't provide any additional information as the project ended, it is fine for me to close this issue 😢 |
Description
Unfortunately we hat do remove the Docker Maven Plugin from our project, as the support of buildx lead to unwanted additional images in the OCI index.
Each image we build had a tiny additional image in its OCI index listet without architecture and OS inforamation. Furthermore Trivy was unable to scan it because of errors.
As a successfull Trivy scan is required for an image to promoted to the next stage, I had to decide to kick out the plugin and to replace it by calls to
docker ...
via the Maven Exec Plugin.Here is a screenshot from Harbor
Info
mvn -v
) :As this is a company internal project, I can't provide the hole project, but here is the plugin configuration:
The text was updated successfully, but these errors were encountered: