[stork-users] Stork 1.19 on RHEL 8 - GLIBC error

[Slawek Figiel]

Hello Dan!

Thank you for your report. It is serious problem. We will fix it.

We recently upgraded the operating system in our CI, which we use to 
build Red Hat UBI 9 packages. We didn't expect it to have any side 
effects, but it seems the  GLIBC version in this OS is newer than the 
one on RHEL 8. Stork depends on the GLIBC version because Golang's 
standard library relies on it. Therefore, you cannot run the binaries in 
an environment with older GLIBC.

We had similar problems with the DEB packages and Ubuntu OS, so we 
already know how to fix it. I opened 
https://gitlab.isc.org/isc-projects/stork/-/issues/1538 to handle it.

We will analyze the possibility of re-building our 1.19 packages and 
re-release them, at least for the RPM packages, but I cannot guarantee it.

Regards,
Slawek Figiel

On 03/10/2024 16:07, Dan Oachs wrote:
> I tried to update the stork agent from 1.18 to 1.19 on my RHEL 8.10 
> system and when the stork agent service tries to start, it fails.  The 
> error message indicates it requires a version of GLIBC that my RHEL 8 
> system does not have.
> 
> stork-agent[2930413]: /usr/bin/stork-agent: /lib64/libc.so.6: version 
> `GLIBC_2.32' not found (required by /usr/bin/stork-agent)
> stork-agent[2930413]: /usr/bin/stork-agent: /lib64/libc.so.6: version 
> `GLIBC_2.34' not found (required by /usr/bin/stork-agent)
> 
> I ran the upgrade by using DNF and my install/updates have all been done 
> with the cloudsmith repo.
> 
> My quick fix for now was to roll back the update and go back to 1.18.
> 
> glibc 2.28 appears to be the latest version my RHEL 8.10 system can find.
> 
> Thanks,
>     Dan Oachs
> 
>