search

quarkusio / quarkus-images

Set of container images delivered for Quarkus
Apache License 2.0
115 stars 76 forks source link

CI is broken due to dependency updates #189

Closed galderz closed 2 years ago

galderz commented 2 years ago

CI builds fail as a result of the tooling image failing with:

2022-04-13 16:18:21,646 docker_builder.py:108        INFO  Docker: Error: 
2022-04-13 16:18:21,647 docker_builder.py:108        INFO  Docker:  Problem: libstdc++-devel-8.5.0-12.el8.i686 has inferior architecture
2022-04-13 16:18:21,648 docker_builder.py:108        INFO  Docker:   - package gcc-c++-8.5.0-12.el8.x86_64 requires libstdc++-devel = 8.5.0-12.el8, but none of the providers can be installed
2022-04-13 16:18:21,649 docker_builder.py:108        INFO  Docker:   - cannot install both libstdc++-devel-8.5.0-10.el8.x86_64 and libstdc++-devel-8.5.0-12.el8.x86_64
2022-04-13 16:18:21,649 docker_builder.py:108        INFO  Docker:   - cannot install both libstdc++-devel-8.5.0-12.el8.x86_64 and libstdc++-devel-8.5.0-10.el8.x86_64
2022-04-13 16:18:21,650 docker_builder.py:108        INFO  Docker:   - libstdc++-devel-8.5.0-10.el8.i686 has inferior architecture
2022-04-13 16:18:21,650 docker_builder.py:108        INFO  Docker:   - package libstdc++-static-8.5.0-10.el8.x86_64 requires libstdc++-devel = 8.5.0-10.el8, but none of the providers can be installed
2022-04-13 16:18:21,651 docker_builder.py:108        INFO  Docker:   - cannot install the best candidate for the job
2022-04-13 16:18:21,651 docker_builder.py:108        INFO  Docker: (try to add '--allowerasing' to command line to replace

This is caused because cekit builds are not reproducible. Up to 3 days ago, epel-release-latest resolved to glibc-devel version 2.28-196.el8 but it now resolves to 2.28-197.el8 which causes this issue (see before and after).

One way to fix it might be to nail the epel-release in use, instead of using latest.

galderz commented 2 years ago

Correction: the difference is likely coming from centos8:stream updates, not epel.

cescoffier commented 2 years ago

Hum, that's somewhat new (as Sunday build passed), but not surprising.

Once in a while one of the images we use get updated in a non compatible way. My only way to find the reason is to read pages of release notes, to try to understand.

cescoffier commented 2 years ago

Actually with your analysis (thanks for this!), we should be able to work around it.