Bitwarden - Docker - QNAP - Virtual Interfaces after reboot

[netcrystals]

Steps To Reproduce

1. Install Bitwarden on q QNAP.
2. Start Bitwarden from command shell using "./bitwarden.sh start"
3. Bitwarden should work properly
4. Check Virtual Interfaces in the "Network- and virtual switch app". Bitwarden should have two virtual switches, one belonging to one of the two nets.
5. Reboot QNAP
6. After QNAP rebooted, Container station is started automatically and Bitwarden containers should also start automatically because restart is set to "always"
7. Check "Network- and virtual switch app", multiple virtual interfaces are created.

Expected Result

I expected that Bitwarden again creates the two networks and attaches its containers to the two networks. It seems as if bitwarden causes the creation of other virtual interfaces on QNAP.

Actual Result

Virtual interfaces that should not be created are created. Honestly speaking, I tried to figure out if other applications or modules are responsible for this behaviour. Perhaps my docker system is destroyed.

Screenshots or Videos

No response

Additional Context

No response

Build Version

2023.10.2

Environment

Self-Hosted

Environment Details

• Linux
• QNAP TS-451+
• docker from QNAPs container station

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.