Pomerium 0.21.2-1 fails to start due to envoy requiring newer GLIBC version

Support
1

What happened?

Pomerium fails to start after update to pomerium-1:0.21.2-1.x86_64

What did you expect to happen?

That pomerium would continue to function after the update

How’d it happen?

  1. Ran yum update

  2. Saw error /tmp/pomerium-envoy3051611832/envoy: /lib64/libm.so.6: version 'GLIBC_2.29' not found (required by /tmp/pomerium-envoy3051611832/envoy)

What’s your environment like?

  • Pomerium version (retrieve with pomerium --version):
    pomerium: 0.21.2-1677177246+1af749e2
    envoy: 1.24.0+05e1343657086268edaa16a1e8a1429d9c8f6e50a44f492cf629fdc71da2ecdc

  • Server Operating System/Architecture/Cloud:
    RHEL 8.7

What did you see in the logs?

{"service":"envoy","name":"envoy","time":"2023-03-29T08:37:01+02:00","message":"/tmp/pomerium-envoy3051611832/envoy: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/pomerium-envoy3051611832/envoy)"}
2

Envoy releases are followed from upstream, we do not custom build them.

RHEL 8.7 has GLIBC 2.28, one minor version shy of what’s required for envoy 1.24

You may either upgrade to RHEL 9.1 or use a previous Pomerium release v0.20.x that uses envoy 1.23