First of all, I’m well aware that at this point TrueNAS containers are an experimental feature, and I’m not using them for anything “mission critical.”
That said, I’m getting an error every few seconds, both at the shell prompt and in /var/log/error, when the single container configured in this box is active (Debian Trixie, running a Samba domain controller for testing and validation only):
Stack trace of thread 308:
#0 0x00007fb054f7d95c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9495c)
ELF object binary architecture: AMD x86-64
2026 May 5 16:33:29 morto Process 1977560 (smbd[192.168.44) of user 2147000001 dumped core.
Stack trace of thread 309:
#0 0x00007fb054f7d95c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9495c)
ELF object binary architecture: AMD x86-64
2026 May 5 16:33:31 morto Process 1977578 (smbd[192.168.44) of user 2147000001 dumped core.
Stack trace of thread 310:
#0 0x00007fb054f7d95c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9495c)
ELF object binary architecture: AMD x86-64
2026 May 5 16:33:33 morto Process 1977595 (smbd[192.168.44) of user 2147000001 dumped core.
Stack trace of thread 311:
#0 0x00007fb054f7d95c n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9495c)
ELF object binary architecture: AMD x86-64
The message appears every few seconds, but not always at the same intervals; as soon as the container is switched off, the log messages stop.
There are no other apparent issues with this machine, and it has been performing well and predictably, with no logged errors, over the past three years.
Look at samba logs in container to see why it’s dumping core. It might be something as simple as SMB_ASSERT due to container / application not being able to do something required.
Your reply is much appreciated! I’ll investigate this further - it was a quick, “just click Next” container creation; I have not delved into the intricacies of its options.
