SNMPv3 Trap on Docker Deployment

[GetMeSomeCoffee]

Hello everyone,
I'm currently struggling with getting SNMPv3 traps to work.
The deployment is completly dockerized and version 6.0.14 for the server-container and the snmp-container.
SNMP traps v1 are working fine but v3 are not registered at all. v3 is running with authentication and privacy protocol (regular value collection working fine).
I came across the following guide with some info about "engine id" but sadly I couldn't make out of it what i have to do in a containerized environment because the mentioned configuration are in a file that would not persist between containers: freedom and integrity of monitoring (zabbix.com)
Has someone else maybe run into the same issue and maybe solved it/found a workaround?
Thank you.

[_na_na_]

Hi, i had the same problem and managed it.
( i believe there might be better solution...)

first, I used net-snmp-create-v3-user command but it didn't work since it used "oldEnginID" of zabbix server itself.
*you can see it in /var/lib/snmp/snmptrapd.conf
however it is required that enginID of snmptrap sender.

Then I updated /etc/snmp/snmptrapd.conf manually** and restarted container twice***.

**createUser -e 0x8000000001020304 traptest SHA mypassword AES
authuser log,execute traptest

***i don't know but just 1 time restart don't work

This way is not for Docker container, but i have no other idea...