CONFIG: Incorrect value for --rx argument (-2) on Rocky9 Linux

[BonZur]

openjnpr-container-vmx-vmx1-1 | CONFIG: Incorrect value for --rx argument (-2)
openjnpr-container-vmx-vmx1-1 |
openjnpr-container-vmx-vmx1-1 | /home/pfe/riot/build/app/riot --
openjnpr-container-vmx-vmx1-1 |
openjnpr-container-vmx-vmx1-1 | Application manadatory parameters:
openjnpr-container-vmx-vmx1-1 | --rx "(PORT, QUEUE, IXPORT, LCORE), ..." : List of NIC RX ports and
openjnpr-container-vmx-vmx1-1 | queues handled by the I/O RX lcores
openjnpr-container-vmx-vmx1-1 | --tx "(PORT, LCORE), ..." : List of NIC TX ports handled by the I/O TX
openjnpr-container-vmx-vmx1-1 | lcores
openjnpr-container-vmx-vmx1-1 | --w "LCORE, ..." : List of the worker lcores
openjnpr-container-vmx-vmx1-1 | --f "LCORE, ..." : Flow manager lcore

[BonZur]

if I enable lite mode at the startup it fails at INIT: The socket number is huge instead of 0 as on my other Machine with same OS but 1 NUMA node and les cores

INIT: Creating ring to connect Scheduler with TX port 0 (through I/O lcore 1) (socket 4294967295) ring :app_sched_ring_tx_s4294967295_p ...
openjnpr-container-vmx-vmx1-1  | PANIC in app_init_create_tx_sched_rings():
openjnpr-container-vmx-vmx1-1  | Cannot create scheduler ring with TX port 0
openjnpr-container-vmx-vmx1-1  | 7: [/home/pfe/riot/build/app/riot() [0x412daa]]
openjnpr-container-vmx-vmx1-1  | 6: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f31a0f0dc87]]
openjnpr-container-vmx-vmx1-1  | 5: [/home/pfe/riot/build/app/riot() [0x40f1c3]]
openjnpr-container-vmx-vmx1-1  | 4: [/home/pfe/riot/build/app/riot() [0x1098041]]
openjnpr-container-vmx-vmx1-1  | 3: [/home/pfe/riot/build/app/riot() [0x109787c]]
openjnpr-container-vmx-vmx1-1  | 2: [/home/pfe/riot/build/app/riot() [0x40845f]]
openjnpr-container-vmx-vmx1-1  | 1: [/home/pfe/riot/build/app/riot() [0x545386]]
openjnpr-container-vmx-vmx1-1  | start_riot.sh: line 241:  1325 Aborted                 (core dumped) /home/pfe/riot/build/app/riot -c ffffffff -n 2 -m 1024 --file-prefix=riot --lcores='(0)@(4),(1-2)@(2,3)' -c 7 --no-huge --log-level=9 --vdev 'eth_af_packet0,iface=eth1,blocksz=32768,framesz=16384,framecnt=256' --vdev 'eth_af_packet1,iface=eth2,blocksz=32768,framesz=16384,framecnt=256' --vdev 'eth_af_packet2,iface=eth3,blocksz=32768,framesz=16384,framecnt=256' --vdev 'eth_af_packet3,iface=eth4,blocksz=32768,framesz=16384,framecnt=256' --vdev 'eth_af_packet4,iface=eth5,blocksz=32768,framesz=16384,framecnt=256' -- --rx "(0,0,0,1),(1,0,1,1),(2,0,2,1),(3,0,3,1),(4,0,4,1)," --tx "(0,1),(1,1),(2,1),(3,1),(4,1)," --w 2 --rpio "local,3000,3001" --hostif "local,3002" --bsz "(32,32),(32,32),(32,32)"

[BonZur]

The solution is to set Core assignment to single numa node in docker compose file