Docker Container tries to allocate 15TB of memory

[flix42]

The teddycloud Docker container consistently fails to start with an out-of-memory error.
The issue persists across multiple Docker tags (develop_debian, sha-b0e3c8d_ubuntu, latest).

Environment:
Host OS: Fedora 41 (Server Edition)
Docker Version: 27.4.1 (Docker Engine - Community)
Docker Compose Version: v2.32.1
CPU Architecture: x86_64 (lacking AVX)
RAM: 32GB
ulimit -v: unlimited

Expected Behavior:
The teddycloud container should start successfully.

Actual Behavior:

The container fails to start with the following error in the logs: 
teddycloud  | 9ERROR: AddressSanitizer failed to allocate 0xdfff0001000 (15392894357504) bytes at address 2008fff7000 (errno: 12)
teddycloud  | 9ReserveShadowMemoryRange failed while trying to map 0xdfff0001000 bytes. Perhaps you're using ulimit -v
teddycloud  | /docker-entrypoint.sh: line 24:     9 Aborted                 (core dumped) teddycloud
teddycloud  | 8ERROR: AddressSanitizer failed to allocate 0xdfff0001000 (15392894357504) bytes at address 2008fff7000 (errno: 12)
teddycloud  | 8ReserveShadowMemoryRange failed while trying to map 0xdfff0001000 bytes. Perhaps you're using ulimit -v
teddycloud  | /docker-entrypoint.sh: line 24:     8 Aborted                 (core dumped) teddycloud
teddycloud exited with code 0
...
teddycloud exited with code 134

Additionally, dmesg shows: "__vm_enough_memory: pid: 673157, comm: teddycloud, not enough memory for the allocation"
Given that the container asks for 15TB of memory this does not seem surprising.

Memory should not be a problem:

free -hm
               total        used        free      shared  buff/cache   available
Mem:            30Gi        16Gi       544Mi       276Mi        13Gi        13Gi
Swap:          145Gi       592Mi       144Gi

Can anyone reproduce this?

[flix42]

Got the container running on a different host.
If this is still interesting enough to be debugged let me know if you need additional information otherwise feel free to close it.

[g3gg0]

is there some more in the logs? like a stack trace or such?

[flix42]

Unfortunately not, this is the full output from "docker compose logs".
Is there a debug/verbose flag?