We use ckan within our organisation and have just switched to the ckan/ckan-base:2.10-py3.1 image. With in our organisation we have a Trivy scan on the image before we can move them to production. Since last week the image is not passing the scan any more because of the following vulnerable os packages:
7 significantly vulnerable os packages for which A FIX IS AVAILABLE:
- libpython3.11-minimal
- libpython3.11-stdlib
- linux-headers-6.1.0-28-common
- linux-kbuild-6.1
- python3-pkg-resources
- python3.11
- python3.11-minimal
We already tried the latest build of master ckan/ckan-base:master-py3.10, which is passing the Trivy scan. On what for timeline can we expect the ckan/ckan-base:2.10-py3.10 to be updated to solve this os packages?
We use ckan within our organisation and have just switched to the ckan/ckan-base:2.10-py3.1 image. With in our organisation we have a Trivy scan on the image before we can move them to production. Since last week the image is not passing the scan any more because of the following vulnerable os packages:
7 significantly vulnerable os packages for which A FIX IS AVAILABLE:
We already tried the latest build of master ckan/ckan-base:master-py3.10, which is passing the Trivy scan. On what for timeline can we expect the ckan/ckan-base:2.10-py3.10 to be updated to solve this os packages?