Hello,
the latest image for this application on docker hub is currently at an age of 4 month (2024-11-14, latest / v0.6.2). When we simply pull the image and do a security scan (integrated scanner in IBMs container registry) we find in total 495 problems/CVEs. These are mainly caused by the dependency linux-libc-dev. When I rebuild the image based on the source code, the CVEs disappear.
I do not want to build the image on my own everytime I deploy the app but I want to use the published image via docker hub which makes it quite comfortable to use. The request is if you could integrate like a (maybe daily) cronjob for the build and publish process of the image and so provide an allways up to date image which can be used in our pipelines.
For the beginning a refreshed version on Docker Hub would be great.
Thank you for this product and your reply!
Hello,
the latest image for this application on docker hub is currently at an age of 4 month (2024-11-14,
latest/v0.6.2). When we simply pull the image and do a security scan (integrated scanner in IBMs container registry) we find in total 495 problems/CVEs. These are mainly caused by the dependencylinux-libc-dev. When I rebuild the image based on the source code, the CVEs disappear.I do not want to build the image on my own everytime I deploy the app but I want to use the published image via docker hub which makes it quite comfortable to use. The request is if you could integrate like a (maybe daily) cronjob for the build and publish process of the image and so provide an allways up to date image which can be used in our pipelines.
For the beginning a refreshed version on Docker Hub would be great.
Thank you for this product and your reply!