vIOSL2 -- SSH Unable to Connect to Image

[Propulsions]

Relatively new to this product so may be user error but nonetheless, using official Cisco vios (router) and viosl2 (switch) images exported from a Cisco VIRL install.

I'm able to build and spin up the images using the makefile README instructions.

ICMP echo requests work to the target hostname(s), IPv4, & IPv6 address.

However, SSH fails with a "Connection Reset by Peer" error after around roughly two minutes.

11:03:15 INFO Containerlab started version=0.69.3
11:03:15 INFO Parsing & checking topology file=vios_switches.clab.yaml
11:03:15 INFO Creating lab directory path=/home/propulsion/vios_switches/clab-vios_switches
11:03:15 INFO Creating container name=viosl2-1
11:03:15 INFO Adding host entries path=/etc/hosts
11:03:15 INFO Adding SSH config for nodes path=/etc/ssh/ssh_config.d/clab-vios_switches.conf
Failed fetching latest version information
╭─────────────────────────────┬────────────────────────────┬────────────────────┬───────────────────╮
│             Name            │         Kind/Image         │        State       │   IPv4/6 Address  │
├─────────────────────────────┼────────────────────────────┼────────────────────┼───────────────────┤
│ clab-vios_switches-viosl2-1 │ linux                      │ running            │ 172.20.20.4       │
│                             │ vrnetlab/cisco_viosl2:15.2 │ (health: starting) │ 3fff:172:20:20::4 │
╰─────────────────────────────┴────────────────────────────┴────────────────────┴───────────────────╯
propulsion@lnx1phx1:~/vios_switches$ssh clab-vios_switches-viosl2-1 
kex_exchange_identification: read: Connection reset by peer
Connection reset by 172.20.20.4 port 22
propulsion@lnx1pxl1:~/vios_switches$

YAML Configuration File

propulsion@lnx1phx1:~/vios_switches$ cat *.yaml
name: vios_switches

topology:
  kinds:
    linux:
      image: vrnetlab/cisco_viosl2:15.2
  nodes:
    viosl2-1:
      kind: linux
      env:
        HOSTNAME: viosl2-1

Thanks!

[leec-666]

It says (health: starting) so the default config which sets up SSH might not have been applied yet. Wait until it says running (healthy) and if it doesn't, check the logs. You should see it sending these commands at some point: https://github.com/srl-labs/vrnetlab/blob/master/cisco/viosl2/docker/launch.py#L128-L174.

Occasionally some of my vrnetlab images hang during this and require a restart which resolves it.