No, we need sanitizer builds to be portable.
E.g. I build a binary on my machine and scp to server.

This was a temporary solution.
Since now LSan does not work at all, and to be worked non-portable LSan is better then portable not worked.
Besides it is likely to be portable, at least if glibc will not be too old on the destination server.

Ok.

Another solution is to implement your own dynamic loader.

AST fuzzer (ASan, actions) — Task failed: $?=137

SIGKILL (137-128=9)

Integration tests (asan, actions) [1/3] — fail: 3, passed: 642, flaky: 0

    E               Exception: Command ['docker', 'exec', '-u', '0', 'roottestbackupwithothergranularity_node1_1', 'bash', '-c', 'clickhouse server --config-file=/etc/clickhouse-server/config.xml --log-file=/var/log/clickhouse-server/clickhouse-server.log  --errorlog-file=/var/log/clickhouse-server/clickhouse-server.err.log --daemon'] return non-zero code 1: clickhouse: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by clickhouse)

clickhouse-server:19.4.5.35 image uses ubuntu:18.04 and it has incompatible glibc, no good.