HAProxy external health checks being killed (running in Docker)

I tried verifying it, but it didn’t reproduce.

Did something like the OOM killer trigger in dmesg?

[redadmin@alma9 ~]$ git clone https://gist.github.com/nmcc1212/ddf90e337653da1b8d3f6a73436b73c9
Cloning into 'ddf90e337653da1b8d3f6a73436b73c9'...
remote: Enumerating objects: 5, done.
remote: Total 5 (delta 0), reused 0 (delta 0), pack-reused 5 (from 1)
Receiving objects: 100% (5/5), done.
[redadmin@alma9 ~]$ ll
total 0
drwxr-xr-x. 3 redadmin redadmin 87 Oct  8 20:34 ddf90e337653da1b8d3f6a73436b73c9
[redadmin@alma9 ~]$ cd ddf90e337653da1b8d3f6a73436b73c9/
[redadmin@alma9 ddf90e337653da1b8d3f6a73436b73c9]$ chmod +x primary-check.sh
[redadmin@alma9 ddf90e337653da1b8d3f6a73436b73c9]$ docker compose up
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
>>>> Executing external compose provider "/usr/bin/podman-compose". Please see podman-compose(1) for how to disable this message. <<<<

a15da03073eac72dbd37d16ba9310114f4eb849d581d5d6cf25b00af14391709
✔ docker.io/library/haproxy:3.2
Trying to pull docker.io/library/haproxy:3.2...
Getting image source signatures
Copying blob 4f4fb700ef54 done   |
Copying blob 8c7716127147 done   |
Copying blob bbc9e592cadb done   |
Copying blob d5223d15135d done   |
Copying blob c9f3668e4cd0 done   |
Copying blob 30862e038e91 done   |
Copying config 52ca014edb done   |
Writing manifest to image destination
a944359c443a241d0a589c5875b235cf4b70d23a0683d2dc35dc7d309cbd9181
[haproxy] | [NOTICE]   (1) : Initializing new worker (3)
[haproxy] | [NOTICE]   (1) : Loading success.
[haproxy] | my test
[haproxy] | my test
[haproxy] | my test
[haproxy] | my test
[haproxy] | my test
[haproxy] | my test