-
Notifications
You must be signed in to change notification settings - Fork 26
Future of this image #416
Comments
It will be built automatically as today.
How do you build your own images of other things?
How many of these CVEs are because of the tool versions? To my knowledge we're not using any EOL versions, and there aren't that many outdated here: #5 |
Thank you fro clarification. The build of other Images is really complicated. Every image we use has to be scanned and if there are CVEs we have to explain if they are important for our use case and so on. The same procedure is with binaries like golang. So it is really no fun. But anyways, looks like most of the CVEs are because of maven (3.0.5 version is installed and currently the version is 3.8.5) and gradle(old major version) Maybe you can update those :) |
i don't see maven installed at all. |
@rarkins i think it's safe to update Gradle, as most users are using the local wrapper anyways |
We don't explicitly install |
image will stay for some more time and build is moved to main repo |
@rarkins
Can you please explain what is the plan about the full image?
In our organization we can not use the slim-image with Docker socket because our build infrastructure is air gaped (we can not just pull everything from the internet)
For this purpose the full image is really useful. The problem is that it is not being updated with the new versions of the tools (maven, gradle, php etc.)
Here is a list of the CVEs that the current tool versions have (it is long):
Vulnerabilities:
The text was updated successfully, but these errors were encountered: