Native .deb package for v2.0.0 requires GLIBC_2.39, breaks on Debian 12 (bookworm)

[kchudy]

Discussed in #2953

^{Originally posted by NerijusRazvodovskis May 19, 2026}
Hi team,

We were preparing to roll out DefGuard v2 on our staging environment and hit a runtime failure on Debian 12:

May 19 12:10:49 fr-int-stage-defguard1.labas.io defguard[236305]: /usr/bin/defguard: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found (required by /usr/bin/defguard)

It looks like the v2.0.0 .deb was built on Debian 13 (trixie), which ships glibc 2.39, while bookworm is on 2.36. The v1.x packages ran fine on bookworm, so this is a regression from our point of view.

Debian 12 is supported until June 2028 (LTS), and a lot of infrastructure is still on it. Since you ship native .deb packages, it would be great to keep bookworm as a supported target — building on bookworm (or in a bookworm-based CI container) would produce a binary that runs on both 12 and 13.

I didn't checked yet, but i believe the same would be for the proxy and for the gateway packages too...

What do you think?

Thank you

Implement workflows for building additional packages (with _ubuntu-22-04-lts.deb suffix) and upload them to APT repository on bookworm distribution.

• Core
• Proxy
• Gateway