I tested the same scenario in VyOS 2025.03.09-0613-rolling and did not observe the same issue.
VyOS works as expected and commit did not get stuck.

There are around 300 interfaces:

• around 200 vxlan interface
• around 30 bridge interfaces
• around 30 Pseudo-Ethernet/MACvlan interfaces
• around 16 Ethernet interfaces
• around 30 Bridge interfaces

https://github.com/vyos/vyos-1x/pull/4171

Only worked:

1. Reboot instance
2. load /config/config.boot
3. sudo podman rm suricata
4. commit

Then it works

vyos@VyOS-Test01#
[edit]
vyos@VyOS-Test01# load /config/config.boot
[edit]
vyos@VyOS-Test01#
[edit]
vyos@VyOS-Test01# compare
+ container {
+     name suricata {
+         allow-host-networks
+         arguments "-q 1"
+         capability "net-admin"
+         capability "sys-admin"
+         capability "sys-nice"
+         image "jasonish/suricata:6.0.14"
+         memory "1024"
+         volume ETC {
+             destination "/etc/suricata"
+             source "/config/suricata/etc"
+         }
+         volume LOGS {
+             destination "/var/log/suricata"
+             source "/config/suricata/logs"
+         }
+         volume RULES {
+             destination "/var/lib/suricata/rules/"
+             source "/config/suricata/rules"
+         }
+     }
+ }

If service is 'failed' state

vyos@VyOS-Test01:~$ systemctl status vyos-container-suricata.service
× vyos-container-suricata.service - VyOS Container suricata
     Loaded: loaded (/run/systemd/system/vyos-container-suricata.service; static)
     Active: failed (Result: exit-code) since Fri 2024-08-23 10:32:44 UTC; 43s ago
   Duration: 4min 55.702s
    Process: 2855 ExecStartPre=/bin/rm -f /run/vyos-container-suricata.service.pid /run/vyos-container-suricata.service.cid (code=exited, sta>
    Process: 2856 ExecStart=/usr/bin/podman run --conmon-pidfile /run/vyos-container-suricata.service.pid --cidfile /run/vyos-container-suric>
    Process: 2867 ExecStopPost=/usr/bin/podman rm --ignore -f --cidfile /run/vyos-container-suricata.service.cid (code=exited, status=0/SUCCE>
    Process: 2873 ExecStopPost=/bin/rm -f /run/vyos-container-suricata.service.cid (code=exited, status=0/SUCCESS)
        CPU: 129ms

You are right there is an op-mode command to restart the container

restart container suricata

But I think there needs to be some checks/changes at least someone will execute the native Podman command to restart the container.

https://github.com/vyos/vyatta-cfg-firewall/pull/37

Tested in VyOS 1.4.0-rc1 , VyOS 1.3.5 and VyOS 1.5-rolling-202401030023
The configuration
VyOS 1.4.0-rc1:

Tested in VyOS 1.3.4

Tested in VyOS 1.3.4

Tested in VyOS 1.4-rolling-202311100309

Tested in VyOS 1.4-rolling-202311100309

Tested on VyOS 1.4-rolling-202311100309

• IKEv1
• 2 proposals
• the pfs is enabled

Tested in VyOS 1.4-rolling-202311100309:

Tested in VyOS 1.4-rolling-202311100309
Configs:
Node-1

Tested on VyOS 1.4-rolling-202311100309:

Tested in VyOS 1.4-rolling-202311100309:
The configuration:

Tested in VyOS 1.4-rolling-202311100309
The configuration:
VyOS:

Tested in VyOS 1.4-rolling-202311100309:
Configurations:

Tested on VyOS 1.4-rolling-202311100309 and VyOS 1.5-rolling-202311160736 - L-Time shows 0. But supposed to show 3600 according to the configuration.

Tested in VyOS 1.4-rolling-202311100309 (AES)

Tested in VyOS 1.4-rolling-202311100309 (3DES)

In VyOS 1.3.4
Configs:

I tested in VyOS 1.4-rolling-202311100309

Tested in VyOS 1.4-rolling-202311100309
Tried with single quotes: ''

Tested VyOS 1.4-rolling-202311100309

Used one of the latest rolling releases.
Configured the Radius server and VyOS

Checked in VyOS 1.4-rolling-202310030309

LEFT router configuration