jib VS cyclonedx-gradle-plugin

You need to build Docker images for each app. This is specific to the JHipster application used in this tutorial which uses Jib to build the images. Make sure you are logged into Docker using docker login. Navigate to each app folder (store, invoice, product) and run the following command:

JIB

It is pretty easy to do with https://github.com/GoogleContainerTools/jib.

Save yourself the dockerfile and use jib: https://github.com/GoogleContainerTools/jib/tree/master/jib-maven-plugin

I first learned about Distroless because it was the default option in Google's Jib. Jib is a Maven plugin to create Docker containers without dependency on Docker. Note that the default has changed now.

Optimize your Dockerfile by using a small base Java Image, use either Spring Boot's layers tools or Google Jib to build your docker file, and increase CPU/Memory requests and limits if you can.

In this section, we will setup the automated generation and deployment of a Docker container image. You will need a Docker Hub account and the Jib Gradle Plugin.

If you don't want to hack on your own scripts to package your app into a container, I can recommend the JIB maven plugin. A gradle version is also available.

There is a CyconeDX plugin available for Gradle. Just like the Maven plugin we discussed earlier, the Gradle plugin is released by the CycloneDX organization on Github with some of the same maintainers as the Maven plugin.

I am not sure if it fits your use case https://github.com/CycloneDX/cyclonedx-gradle-plugin

OP - rather than jumping in with a “solution”, I would be Irving you to use this as an opportunity for change in your company to improve the governance around software installation in your company (a software catalog and white listing applications would be the best approach), reduce the exposure of licensing costs (or pirated software) in your environment and simplify your ongoing support requirements. Software Bill Of Materials software such as Cyclone DX as a possible solution to collate the information along with vulnerability information, to focus on the known vulnerabilities vs oldest software would be my recommendation. This is a priority in the US under the Executive Order 14208 to improve the nations’s cyber security - The minimum requirements for a Software Bill Of Materials.

I think CycloneDX [1] is the go-to SBOM specification these days.

[1] https://cyclonedx.org/