You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a new cataloger specifically for GitLab installations. In the GitLab official images there is a RELEASE file in the root of the filesystem that identifies the GitLab installation and version. There is also a more detailed manifest file detailing the installation and vendored dependencies at /opt/gitlab/version-manifest.json
For docker.io/gitlab/gitlab-ce:15.6.1-ce.0@sha256:04d4219d5dfb3acccc9997e50477c8d24b371387a95857e1ea8fc779e17a716c:
Currently syft will pick up that GitLab is installed as a Debian package; however, this leads to problems later on in grype when trying to match vulnerabilities because it will match against the Debian security feed and since GitLab isn't actually a Debian-supported package it will never find any relevant matches. I'm not sure what the best solution is to that case in general, but for GitLab specifically it feels like there could be value in creating a dedicated cataloger that might be able to account for this and also pick up on the extra dependency relationship details embedded in the manifest file.
Additional context:
I think I spoke to @wagoodman about this quite some time ago but forgot to capture an issue for it
The text was updated successfully, but these errors were encountered:
What would you like to be added:
Create a new cataloger specifically for GitLab installations. In the GitLab official images there is a RELEASE file in the root of the filesystem that identifies the GitLab installation and version. There is also a more detailed manifest file detailing the installation and vendored dependencies at
/opt/gitlab/version-manifest.json
For
docker.io/gitlab/gitlab-ce:15.6.1-ce.0@sha256:04d4219d5dfb3acccc9997e50477c8d24b371387a95857e1ea8fc779e17a716c
:/RELEASE
/opt/gitlab/version-manifest.json
Why is this needed:
Currently syft will pick up that GitLab is installed as a Debian package; however, this leads to problems later on in grype when trying to match vulnerabilities because it will match against the Debian security feed and since GitLab isn't actually a Debian-supported package it will never find any relevant matches. I'm not sure what the best solution is to that case in general, but for GitLab specifically it feels like there could be value in creating a dedicated cataloger that might be able to account for this and also pick up on the extra dependency relationship details embedded in the manifest file.
Additional context:
I think I spoke to @wagoodman about this quite some time ago but forgot to capture an issue for it
The text was updated successfully, but these errors were encountered: