Can't commit the command

Bugs
1

vyos@vyos# commit
[ interfaces ethernet eth0 ]
VyOS had an issue completing a command.

We are sorry that you encountered a problem while using VyOS.
There are a few things you can do to help us (and yourself):

When reporting problems, please include as much information as possible:

  • do not obfuscate any data (feel free to contact us privately if your
    business policy requires it)
  • and include all the information presented below

Report time: 2023-07-05 10:03:04
Image version: VyOS 1.3.0-epa2
Release train: equuleus

Built by: Sentrium S.L.
Built on: Sun 17 Oct 2021 17:35 UTC
Build UUID: 2a282866-08cf-40fc-82a1-29ac261d3fb4
Build commit ID: defac161082bc3-dirty

Architecture: x86_64
Boot via: installed image
System type: VMware guest

Hardware vendor: VMware, Inc.
Hardware model: VMware Virtual Platform
Hardware S/N: VMware-56 4d 81 a9 d1 3b d8 7e-b8 f0 ea 7c 34 0c 4b 93
Hardware UUID: a9814d56-3bd1-7ed8-b8f0-ea7c340c4b93

Traceback (most recent call last):
File “/usr/libexec/vyos/conf_mode/interfaces-ethernet.py”, line 161, in
verify(c)
File “/usr/libexec/vyos/conf_mode/interfaces-ethernet.py”, line 73, in verify
ethtool = Ethtool(ifname)
File “/usr/lib/python3/dist-packages/vyos/ethtool.py”, line 60, in init
raise ValueError(f’Could not determine driver for interface {ifname}!')
ValueError: Could not determine driver for interface eth0!

[[interfaces ethernet eth0]] failed
Commit failed
[edit]
vyos@vyos#
[edit]
vyos@vyos#

container environemt:
#!/bin/bash
set -v

cat <clab.yaml | clab deploy -t clab.yaml -
name: routing
topology:
nodes:
gw0:
kind: linux
#image: 192.168.2.100:5000/vyos/vyos:1.2.8
image: 192.168.2.100:5000/vyos/vyos:1.3-epa2
cmd: /sbin/init
binds:
- /lib/modules:/lib/modules
- ./startup-conf/gw0-boot.cfg:/opt/vyatta/etc/config/config.boot

server1:
  kind: linux
  image: 192.168.2.100:5000/nettool
  exec:
  - ip addr add 10.1.5.10/24 dev net0
  - ip route replace default via 10.1.5.1

server2:
  kind: linux
  image: 192.168.2.100:5000/nettool
  exec:
  - ip addr add 10.1.8.10/24 dev net0
  - ip route replace default via 10.1.8.1

links:
- endpoints: [“gw0:eth1”, “server1:net0”]
- endpoints: [“gw0:eth2”, “server2:net0”]

EOF

root@vyos:/# ethtool -i eth0
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
root@vyos:/#

2

It should be fixed in 1.3.3 in this commit

3

thank you sir.
will refer this ticket.

4

Hello sir, do we have a plan to release this image 1.3.3
from the dockerhub, we can see Docker
the latest one is above issue image.
if with this image, we can test more and more feature to let the NOS more successfully.
Thanks a lot.

5

LTS releases won’t be available in docker hub
You can build your own docker image Running in Docker Container — VyOS 1.4.x (sagitta) documentation

6

Sure.
[edit]
vyos@gw0# set interfaces ethernet eth1 address 1.1.1.2/24
[edit]
vyos@gw0# commit
[ interfaces ethernet eth1 ]
sudo: unable to resolve host gw0: System error

[edit]
vyos@gw0#

but it seem like specifical the hostname.
i use containerlab project to create the network topo with below yaml:

cat <<EOF>clab.yaml | clab deploy -t clab.yaml -
name: routing
topology:
  nodes:
    gw0:
      kind: linux
      image: 192.168.2.100:5000/vyos/vyos:1.4.7
      cmd: /sbin/init
      binds:
        - /lib/modules:/lib/modules
        #- ./startup-conf/gw0-boot.cfg:/opt/vyatta/etc/config/config.boot

    server1:
      kind: linux
      image: 192.168.2.100:5000/nettool
      exec:
      - ip addr add 10.1.5.10/24 dev net0
      - ip route replace default via 10.1.5.1

    server2:
      kind: linux
      image: 192.168.2.100:5000/nettool
      exec:
      - ip addr add 10.1.8.10/24 dev net0
      - ip route replace default via 10.1.8.1


  links:
    - endpoints: ["gw0:eth1", "server1:net0"]
    - endpoints: ["gw0:eth2", "server2:net0"]

EOF

how to solve the issue, just set the host-name with gw0.
@Viacheslav thanks you sir.

7

How does your file config look like and do you get the same error if you set the system host-name to something else like just “vyos” or similar?

8

No, if we set the hostname same with yaml. the error will not be appeared.