Investigate php composer segfault in gemnasium analyzer
Summary
The latest code to merge into main branch ran into an issue building the gemnasium
fips image. The error was a segfault in php composer
under the ubi8-minimal
image.
The current fix for this issue is to do a revert back to old code using ubi8
.
The segfault should be investigated and resolved so that the analyzer can continue using the ubi8-minimal
image.
Here's an example crash: https://gitlab.com/gitlab-org/security-products/analyzers/gemnasium/-/jobs/3244872107
Steps to reproduce
docker pull registry.access.redhat.com/ubi8-minimal:8.6-941
docker run -it --rm registry.access.redhat.com/ubi8-minimal:8.6-985
$ microdnf module enable php:8.0 && microdnf install php php-common php-zip php-json php-xml php-mbstring --nodocs
$ curl -o /usr/local/bin/composer https://getcomposer.org/download/2.4.1/composer.phar
$ chmod 755 /usr/local/bin/composer
$ /usr/local/bin/composer
Segmentation fault (core dumped)
What is the current bug behavior?
segfault
occurs: https://gitlab.com/gitlab-org/security-products/analyzers/gemnasium/-/jobs/3244872107
What is the expected correct behavior?
The image should build without errors.
Possible fixes
It's likely an upstream issue that will be resolved in the latest ubi8-minimal
but resolution should also involve the root cause of the failure and documentation as to how to resolve such errors in the future (if not mitigate automatically).