system is renaming docker interfaces which causes the network to stop wotking

Recently after replacing an HBA and booting my server running OMV5 I noticed that it won't connect to the network anymore. Not even the ethernet LEDs would light up. Upon checking dmesg I got the following:

[ 27.013796] eth0: renamed from veth3acd072
[ 27.123315] eth0: renamed from veth2c7a204
[ 934.731916] veth3acd072: renamed from eth0
[ 934.996108] veth7298456: renamed from eth1
[ 1310.256532] eth0: renamed from vetha02b746

I know what this problem is as I have experienced it on Raspberry Pi SBCs. It has to do with the system picking up the virtual interfaces created by Docker. The fix for it is normally easy:
Just adding denyinterfaces veth* to /etc/dhcpcd.conf or editing /etc/NetworkManager/NetworkManager.conf to contain:

[keyfile]
unmanaged-devices=interface-name:veth*

However, I can't do either of those since OMV uses a different networking system.

I tried creating a rule in /etc/systemd/network/99-ignore-veth.network stating:

[Match]
Name=veth*

[Link]
Unmanaged=yes

That did nothing.

Can anyone guide in what I should do in order to replicate the above fix on OMV 5. Thanks.

I am aware that the system is EOL and I should upgrade it, however it's a system at a remote location that I don't have physical access to and the way I interact through it is via a third party, so I put off updating it until I am there to diagnose any possible problems such as this. I will post the output of dpkg -l | grep -iE "dhcp|network" once said 3rd party will be free again to run the command (because I cannot access it remotely due to the completely dead networking)

Yes, the system was installed with the official ISO, the HBA was placed in the same slot where the old HBA was.

No, I exchanged an old unknown HBA (since that one periodically dropped sata devices as of recently) to an LSI Logic SAS3444E.

Below is the output of dpkg -l | grep -iE "dhcp|network" please excuse me omitting the architecture and the description since I had to copy this form an image of the screen.

root@openmediavault:"# dpkg -1 | grep -iE "dhcp/network"
ii atmel-firmare                        1.3-4
ii chrony                               3.4-4+deb10u2
ii dirangr                              2.2.12-1+deb10u2
ii ifupdown                             0.8.35+pve1
ii iproute2                             4.20.0-2+deb10u1
ii iputils-ping                         3:20180629-2+deb10u2
ii isc-dhcp-client                      4.4.1-2+deb10u3
ii isc-dhcp-common                      4.4.1-2+deb10u3
ii libsodium23:amd64                    1.0.17-1
ii netbase                              5.6
ii netplan.io                           0.95-2
ii openmediavault                       5.6.26-1
ii python3-netifaces                    0.10.4-1+b1
root@openmediavault:"#

Back to the original question, is it even possible to replicate the rules I asked about initially in omv or does the networking implementation not offer such capabilities?

Running omv-firstaid and selecting the correct interface seems to have fixed the issue for long enough for me to upgrade to OMV 6.