SONiC is identified with
sonic-vs kind in the topology file. A kind defines a supported feature set and a startup procedure of a
To build a
sonic-vs docker image:
- Leverage automated scripts provided by @antongisli
- or consult with the SONiC build documentation and create the docker images with
sonic-vs nodes launched with containerlab come without any additional configuration.
Getting Sonic images#
Apparently, it is still tricky to find sonic container images, as their prime distribution format is a VM. Several discussions happened around creating a container build pipeline and a few projects were created.
One of the latest known working images can be found here.
Managing sonic-vs nodes#
SONiC node launched with containerlab can be managed via the following interfaces:
sonic-vs container uses the following mapping for its linux interfaces:
eth0- management interface connected to the containerlab management network
eth1- first data (front-panel port) interface
When containerlab launches sonic-vs node, it will assign IPv4/6 address to the
eth0 interface. Data interface
eth1 mapped to
Ethernet0 port and needs to be configured with IP addressing manually. See Lab examples for exact configurations.
The following labs feature sonic-vs node: