Skip to content

Cumulus Linux (docker runtime) and Host

Description Cumulus Linux in Docker runtime connected to a Host
Components Cumulus Linux
Resource requirements[^1] 1
1 GB
Topology file topo.clab.yml
Name cvx02
Version information[^2] cvx:4.3.0 docker-ce:19.03.13


The lab consists of Cumulus Linux running in its non-default, docker runtime, connected to a linux container playing the role of an end-host. Both nodes are also connected to the clab docker network over their management eth0 interfaces.


Both nodes have been provided with a startup configuration and should come up with all their interfaces fully configured.

Once the lab is started, the nodes will be able to ping each other:

$  clab-cvx02-sw1
Warning: Permanently added 'clab-cvx02-sw1,2001:172:20:20::3' (ECDSA) to the list of known hosts.
root@clab-cvx02-sw1's password:
Linux sw1 #17 SMP Mon May 24 15:22:51 BST 2021 x86_64
root@sw1:mgmt:~# ping switching to vrf "default"; use '--no-vrf-switch' to disable
PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=64 time=0.297 ms
--- ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.297/0.297/0.297/0.000 ms

Use cases#

  • Demonstrate how a cvx node can run in its non-default docker runtime
  • Demonstrate how to inject startup configuration into a cvx node.
  • Verify basic control plane and data plane operations