Hi, thanks for reply!
I use cURL in Gitlab CI/CD job to utilize secure files. I must get the download-secure-files tool to download the files in the job. So example code looks like this:
Installation of new packages via apk are now more complicated since entrypoint in container started from newest image (10) run commands as regular user (not root). Also building custom image only for get cURL is in my opinion pointless.
Iâll pass on the feedback to the right place. Thanks for your patience, and keep using the older version if you need (not that you need my permission )
thanks for the feedback we consider every input from our community. To better understand the issue:
Would âwgetâ, which is already available on the image, work for you for that specific use case?
We would like to support you with a usable image as much as possible, but we also need to limit unused packages and possible sources of security vulnerabilities.
I know that is not the most convenient solution so far. Is there a reason not to use a separate stage to download the secure files and reuse them in the Sonar step?
I understand that it may be extra work on your side; however, we would like to concentrate on using our image for the scan functionalities.
We will reconsider the packages on the images from time to time, but so far, we would like to keep them in their current form.
Hi,
I understand and acknowledge your point. I will handle it by implementing the workaround you suggested or come up with another solution of my own.
Thank you for your assistance!
I wanted to inform you that we have changed the base image for SonarSource/sonar-scanner-cli in the latest 11 version. It should have curl installed.
The curl here comes from the base image, which will be patched and controlled by AWS. We do not necessarily intend to have a curl on the image, but we will have it until the base image provides it, which seems stable for a while.
The latest tag has not yet been updated, so you need to be specific with the version numbers to have the latest changes.