We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
from https://hub.docker.com/layers/library/sonarqube/lts-community/images/sha256-a05a6ffb12f12058671fd24316faab24b238543502a4d631cd3908700ef2f796?context=repo&tab=vulnerabilities, I can see that the latest images in docker hub contains quite a few vulnerabilities (2 critical, 11 high etc.). Do you have any plans to fix them ? Some of the packages have fixable versions to resolve them according to docker hub. Thanks.
The text was updated successfully, but these errors were encountered:
Hi @othomann,
thanks for raising this issue.
Could you please post your question in our community forum? It will then get triaged to the right team :)
Sorry, something went wrong.
@carminevassallo hi, in what forum specifically should I post the message ? Thanks.
Hi again @othomann,
I was referring to this community forum. Do you have access to the link?
yes, but I mean what forum ? I was about to post a new topic in Product Manager for a Day topics under sonarqube category. Is this the right place ?
Product Manager for a Day topics
Thanks.
I posted https://community.sonarsource.com/t/resolve-vulnerabilities-in-docker-images/115223
carminevassallo
No branches or pull requests
Hi,
from https://hub.docker.com/layers/library/sonarqube/lts-community/images/sha256-a05a6ffb12f12058671fd24316faab24b238543502a4d631cd3908700ef2f796?context=repo&tab=vulnerabilities, I can see that the latest images in docker hub contains quite a few vulnerabilities (2 critical, 11 high etc.).
Do you have any plans to fix them ? Some of the packages have fixable versions to resolve them according to docker hub.
Thanks.
The text was updated successfully, but these errors were encountered: