Attempt to use VPP VyOS in the containerlab
```
admin@vyos1# sudo ethtool -i eth1
driver: veth
version: 1.0
firmware-version:
expansion-rom-version:
bus-info:
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
[edit]
admin@vyos1#
```
Config:
```
dmin@vyos1# set vpp settings interface eth1 driver dpdk
[edit]
admin@vyos1# commit
[ vpp ]
Traceback (most recent call last):
File "/usr/libexec/vyos/services/vyos-configd", line 144, in run_script
c = script.get_config(config)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/libexec/vyos/conf_mode/vpp.py", line 308, in get_config
iface_filter_eth(conf, iface)
File "/usr/lib/python3/dist-packages/vyos/vpp/config_filter.py", line 46, in iface_filter_eth
iface_nodes = config._session_config.list_nodes(['interfaces', 'ethernet', iface])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/vyos/configtree.py", line 373, in list_nodes
raise ConfigTreeError("Path [{}] doesn't exist".format(path_str))
vyos.configtree.ConfigTreeError: Path [b'interfaces ethernet eth1'] doesn't exist
[[vpp]] failed
Commit failed
[edit]
admin@vyos1# run show ver
Version: VyOS 2025.09.27-0018-rolling
Release train: current
Release flavor: generic
Built by: autobuild@vyos.net
Built on: Sat 27 Sep 2025 00:18 UTC
Build UUID: af6c0769-8971-4f88-a9e4-e81f5aa7e246
Build commit ID: 137b20e4253f02
Architecture: x86_64
Boot via: installed image
System type: KVM guest
Secure Boot: n/a (BIOS)
Hardware vendor: QEMU
Hardware model: Standard PC (Q35 + ICH9, 2009)
Hardware S/N:
Hardware UUID: ca1f5536-cdd2-468a-b19b-b26702f81070
Copyright: VyOS maintainers and contributors
[edit]
admin@vyos1#
```
The containerlab topology:
```
$ cat vyos.clab.yml
name: vyos_lab
topology:
#kinds:
# vyosnetworks_vyos:
# startup-config: vyos-custom-startup.cfg
nodes:
# vyos1 will boot with vyos-custom-startup.cfg as set in the kind parameters
vyos1:
kind: vyosnetworks_vyos
image: ghcr.io/sever-sever/vyos-container:latest
# vyos2 will boot with its own specific startup config, as it overrides the kind variables
vyos2:
kind: vyosnetworks_vyos
image: ghcr.io/sever-sever/vyos-container:latest
#startup-config: node-specific-startup.cfg
links:
- endpoints: ["vyos1:eth1", "vyos2:eth1"]
```