Starting docker:dind works but immediatly creates a core dump wihtin the container as /core

With runc this does not happen:

docker run -it --rm --runtime runc --privileged --userns host docker:dind

With sysbox the core dump is created in /core within the container:

docker run -it --rm --runtime sysbox-runc docker:dind

I compared the console output of both commands and saw only these additional lines with sysbox-runc and no sign of the core dump:

[...]
mount: permission denied (are you root?)
Could not mount /sys/kernel/security.
AppArmor detection and --privileged mode might break.
[...]
WARN[2021-04-30T14:17:38.544203142Z] Not using native diff for overlay2, this may cause degraded performance for building images: running in a user namespace  storage-driver=overlay2
[...]

Looking at the core dump i think it comes from a process called /check. But i am not a specialist for core dumps. But i often find this string within it:

strings core 
CORE
CORE
check
/check 
IGISCORE
CORE
ELIFCORE
/check
/check
CORE
FLINUX
LINUX
__kernel_vsyscall
__kernel_sigreturn
__kernel_rt_sigreturn
__vdso_gettimeofday
__vdso_time
__vdso_clock_gettime
__vdso_clock_gettime64
__vdso_clock_getres
linux-gate.so.1
LINUX_2.6
LINUX_2.5
Linux
Linux
5.10.0-0.bpo.5-amd64
B]wB
$[^_]
T[^_]
[^_]
\[^_]
d[^_]
d[^_]
<>9}
[^_]
T[^_]
<>9}
GCC: (Debian 8.3.0-6) 8.3.0
.shstrtab
.gnu.hash
.dynsym
.dynstr
.gnu.version
.gnu.version_d
.dynamic
.rodata
.note
.eh_frame_hdr
.eh_frame
.text
.altinstructions
.altinstr_replacement
.comment
v,M^i686
/check
HOSTNAME=b3aadbefad02
SHLVL=2
HOME=/root
container=docker
DIND_COMMIT=ed89041433a031cafc0a0f19cfe573c31688d377
TERM=xterm
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_VERSION=20.10.6
DOCKER_TLS_CERTDIR=/certs
PWD=/
TMPDIR=/var/lib/docker/tmp
/check